xref: /linux/tools/perf/pmu-events/arch/x86/goldmontplus/memory.json (revision 48dea9a700c8728cc31a1dd44588b97578de86ee)
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        "PEBScounters": "0,1,2,3",
10        "EventName": "MISALIGN_MEM_REF.LOAD_PAGE_SPLIT",
11        "SampleAfterValue": "200003",
12        "BriefDescription": "Load uops that split a page (Precise event capable)"
13    },
14    {
15        "PEBS": "2",
16        "CollectPEBSRecord": "2",
17        "PublicDescription": "Counts when a memory store of a uop spans a page boundary (a split) is retired.",
18        "EventCode": "0x13",
19        "Counter": "0,1,2,3",
20        "UMask": "0x4",
21        "PEBScounters": "0,1,2,3",
22        "EventName": "MISALIGN_MEM_REF.STORE_PAGE_SPLIT",
23        "SampleAfterValue": "200003",
24        "BriefDescription": "Store uops that split a page (Precise event capable)"
25    },
26    {
27        "CollectPEBSRecord": "1",
28        "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.",
29        "EventCode": "0xC3",
30        "Counter": "0,1,2,3",
31        "UMask": "0x2",
32        "PEBScounters": "0,1,2,3",
33        "EventName": "MACHINE_CLEARS.MEMORY_ORDERING",
34        "PDIR_COUNTER": "na",
35        "SampleAfterValue": "20003",
36        "BriefDescription": "Machine clears due to memory ordering issue"
37    }
38]