170ae034dSAndrew Kilroy[ 270ae034dSAndrew Kilroy { 3a484e645SJames Clark "ArchStdEvent": "MEM_ACCESS", 4a484e645SJames Clark "PublicDescription": "Counts memory accesses issued by the CPU load store unit, where those accesses are issued due to load or store operations. This event counts memory accesses no matter whether the data is received from any level of cache hierarchy or external memory. If memory accesses are broken up into smaller transactions than what were specified in the load or store instructions, then the event counts those smaller memory transactions." 570ae034dSAndrew Kilroy }, 670ae034dSAndrew Kilroy { 7a484e645SJames Clark "ArchStdEvent": "MEMORY_ERROR", 8a484e645SJames Clark "PublicDescription": "Counts any detected correctable or uncorrectable physical memory errors (ECC or parity) in protected CPUs RAMs. On the core, this event counts errors in the caches (including data and tag rams). Any detected memory error (from either a speculative and abandoned access, or an architecturally executed access) is counted. Note that errors are only detected when the actual protected memory is accessed by an operation." 9c581e46bSNick Forrington }, 10c581e46bSNick Forrington { 11a484e645SJames Clark "ArchStdEvent": "REMOTE_ACCESS", 12a484e645SJames Clark "PublicDescription": "Counts accesses to another chip, which is implemented as a different CMN mesh in the system. If the CHI bus response back to the core indicates that the data source is from another chip (mesh), then the counter is updated. If no data is returned, even if the system snoops another chip/mesh, then the counter is not updated." 1370ae034dSAndrew Kilroy }, 1470ae034dSAndrew Kilroy { 15a484e645SJames Clark "ArchStdEvent": "MEM_ACCESS_RD", 16a484e645SJames Clark "PublicDescription": "Counts memory accesses issued by the CPU due to load operations. The event counts any memory load access, no matter whether the data is received from any level of cache hierarchy or external memory. The event also counts atomic load operations. If memory accesses are broken up by the load/store unit into smaller transactions that are issued by the bus interface, then the event counts those smaller transactions." 1770ae034dSAndrew Kilroy }, 1870ae034dSAndrew Kilroy { 19a484e645SJames Clark "ArchStdEvent": "MEM_ACCESS_WR", 20a484e645SJames Clark "PublicDescription": "Counts memory accesses issued by the CPU due to store operations. The event counts any memory store access, no matter whether the data is located in any level of cache or external memory. The event also counts atomic load and store operations. If memory accesses are broken up by the load/store unit into smaller transactions that are issued by the bus interface, then the event counts those smaller transactions." 2170ae034dSAndrew Kilroy } 2270ae034dSAndrew Kilroy] 23