xref: /linux/tools/perf/pmu-events/arch/x86/goldmont/memory.json (revision 95298d63c67673c654c08952672d016212b26054)
1[
2    {
3        "PEBS": "2",
4        "CollectPEBSRecord": "2",
5        "PublicDescription": "Counts when a memory load of a uop spans a page boundary (a split) is retired.",
6        "EventCode": "0x13",
7        "Counter": "0,1,2,3",
8        "UMask": "0x2",
9        "EventName": "MISALIGN_MEM_REF.LOAD_PAGE_SPLIT",
10        "SampleAfterValue": "200003",
11        "BriefDescription": "Load uops that split a page (Precise event capable)"
12    },
13    {
14        "PEBS": "2",
15        "CollectPEBSRecord": "2",
16        "PublicDescription": "Counts when a memory store of a uop spans a page boundary (a split) is retired.",
17        "EventCode": "0x13",
18        "Counter": "0,1,2,3",
19        "UMask": "0x4",
20        "EventName": "MISALIGN_MEM_REF.STORE_PAGE_SPLIT",
21        "SampleAfterValue": "200003",
22        "BriefDescription": "Store uops that split a page (Precise event capable)"
23    },
24    {
25        "CollectPEBSRecord": "1",
26        "PublicDescription": "Counts machine clears due to memory ordering issues.  This occurs when a snoop request happens and the machine is uncertain if memory ordering will be preserved as another core is in the process of modifying the data.",
27        "EventCode": "0xC3",
28        "Counter": "0,1,2,3",
29        "UMask": "0x2",
30        "EventName": "MACHINE_CLEARS.MEMORY_ORDERING",
31        "SampleAfterValue": "200003",
32        "BriefDescription": "Machine clears due to memory ordering issue"
33    }
34]