1[ 2 { 3 "ArchStdEvent": "L1D_CACHE_REFILL", 4 "PublicDescription": "Counts level 1 data cache refills caused by speculatively executed load or store operations that missed in the level 1 data cache. This event only counts one event per cache line. This event does not count cache line allocations from preload instructions or from hardware cache prefetching." 5 }, 6 { 7 "ArchStdEvent": "L1D_CACHE", 8 "PublicDescription": "Counts level 1 data cache accesses from any load/store operations. Atomic operations that resolve in the CPUs caches (near atomic operations) counts as both a write access and read access. Each access to a cache line is counted including the multiple accesses caused by single instructions such as LDM or STM. Each access to other level 1 data or unified memory structures, for example refill buffers, write buffers, and write-back buffers, are also counted." 9 }, 10 { 11 "ArchStdEvent": "L1D_CACHE_WB", 12 "PublicDescription": "Counts write-backs of dirty data from the L1 data cache to the L2 cache. This occurs when either a dirty cache line is evicted from L1 data cache and allocated in the L2 cache or dirty data is written to the L2 and possibly to the next level of cache. This event counts both victim cache line evictions and cache write-backs from snoops or cache maintenance operations. The following cache operations are not counted:\n\n1. Invalidations which do not result in data being transferred out of the L1 (such as evictions of clean data),\n2. Full line writes which write to L2 without writing L1, such as write streaming mode." 13 }, 14 { 15 "ArchStdEvent": "L1D_CACHE_RD", 16 "PublicDescription": "Counts level 1 data cache accesses from any load operation. Atomic load operations that resolve in the CPUs caches counts as both a write access and read access." 17 }, 18 { 19 "ArchStdEvent": "L1D_CACHE_WR", 20 "PublicDescription": "Counts level 1 data cache accesses generated by store operations. This event also counts accesses caused by a DC ZVA (data cache zero, specified by virtual address) instruction. Near atomic operations that resolve in the CPUs caches count as a write access and read access." 21 }, 22 { 23 "ArchStdEvent": "L1D_CACHE_REFILL_RD", 24 "PublicDescription": "Counts level 1 data cache refills caused by speculatively executed load instructions where the memory read operation misses in the level 1 data cache. This event only counts one event per cache line." 25 }, 26 { 27 "ArchStdEvent": "L1D_CACHE_REFILL_WR", 28 "PublicDescription": "Counts level 1 data cache refills caused by speculatively executed store instructions where the memory write operation misses in the level 1 data cache. This event only counts one event per cache line." 29 }, 30 { 31 "ArchStdEvent": "L1D_CACHE_REFILL_INNER", 32 "PublicDescription": "Counts level 1 data cache refills where the cache line data came from caches inside the immediate cluster of the core." 33 }, 34 { 35 "ArchStdEvent": "L1D_CACHE_REFILL_OUTER", 36 "PublicDescription": "Counts level 1 data cache refills for which the cache line data came from outside the immediate cluster of the core, like an SLC in the system interconnect or DRAM." 37 }, 38 { 39 "ArchStdEvent": "L1D_CACHE_WB_VICTIM", 40 "PublicDescription": "Counts dirty cache line evictions from the level 1 data cache caused by a new cache line allocation. This event does not count evictions caused by cache maintenance operations." 41 }, 42 { 43 "ArchStdEvent": "L1D_CACHE_WB_CLEAN", 44 "PublicDescription": "Counts write-backs from the level 1 data cache that are a result of a coherency operation made by another CPU. Event count includes cache maintenance operations." 45 }, 46 { 47 "ArchStdEvent": "L1D_CACHE_INVAL", 48 "PublicDescription": "Counts each explicit invalidation of a cache line in the level 1 data cache caused by:\n\n- Cache Maintenance Operations (CMO) that operate by a virtual address.\n- Broadcast cache coherency operations from another CPU in the system.\n\nThis event does not count for the following conditions:\n\n1. A cache refill invalidates a cache line.\n2. A CMO which is executed on that CPU and invalidates a cache line specified by set/way.\n\nNote that CMOs that operate by set/way cannot be broadcast from one CPU to another." 49 } 50] 51