1[
2    {
3        "CollectPEBSRecord": "1",
4        "PublicDescription": "Counts requests to the Instruction Cache (ICache) for one or more bytes in an ICache Line and that cache line is in the ICache (hit).  The event strives to count on a cache line basis, so that multiple accesses which hit in a single cache line count as one ICACHE.HIT.  Specifically, the event counts when straight line code crosses the cache line boundary, or when a branch target is to a new line, and that cache line is in the ICache. This event counts differently than Intel processors based on Silvermont microarchitecture.",
5        "EventCode": "0x80",
6        "Counter": "0,1,2,3",
7        "UMask": "0x1",
8        "EventName": "ICACHE.HIT",
9        "SampleAfterValue": "200003",
10        "BriefDescription": "References per ICache line that are available in the ICache (hit). This event counts differently than Intel processors based on Silvermont microarchitecture"
11    },
12    {
13        "CollectPEBSRecord": "1",
14        "PublicDescription": "Counts requests to the Instruction Cache (ICache)  for one or more bytes in an ICache Line and that cache line is not in the ICache (miss).  The event strives to count on a cache line basis, so that multiple accesses which miss in a single cache line count as one ICACHE.MISS.  Specifically, the event counts when straight line code crosses the cache line boundary, or when a branch target is to a new line, and that cache line is not in the ICache. This event counts differently than Intel processors based on Silvermont microarchitecture.",
15        "EventCode": "0x80",
16        "Counter": "0,1,2,3",
17        "UMask": "0x2",
18        "EventName": "ICACHE.MISSES",
19        "SampleAfterValue": "200003",
20        "BriefDescription": "References per ICache line that are not available in the ICache (miss). This event counts differently than Intel processors based on Silvermont microarchitecture"
21    },
22    {
23        "CollectPEBSRecord": "1",
24        "PublicDescription": "Counts requests to the Instruction Cache (ICache) for one or more bytes in an ICache Line.  The event strives to count on a cache line basis, so that multiple fetches to a single cache line count as one ICACHE.ACCESS.  Specifically, the event counts when accesses from straight line code crosses the cache line boundary, or when a branch target is to a new line.\r\nThis event counts differently than Intel processors based on Silvermont microarchitecture.",
25        "EventCode": "0x80",
26        "Counter": "0,1,2,3",
27        "UMask": "0x3",
28        "EventName": "ICACHE.ACCESSES",
29        "SampleAfterValue": "200003",
30        "BriefDescription": "References per ICache line. This event counts differently than Intel processors based on Silvermont microarchitecture"
31    },
32    {
33        "CollectPEBSRecord": "1",
34        "PublicDescription": "Counts the number of times the Microcode Sequencer (MS) starts a flow of uops from the MSROM. It does not count every time a uop is read from the MSROM.  The most common case that this counts is when a micro-coded instruction is encountered by the front end of the machine.  Other cases include when an instruction encounters a fault, trap, or microcode assist of any sort that initiates a flow of uops.  The event will count MS startups for uops that are speculative, and subsequently cleared by branch mispredict or a machine clear.",
35        "EventCode": "0xE7",
36        "Counter": "0,1,2,3",
37        "UMask": "0x1",
38        "EventName": "MS_DECODED.MS_ENTRY",
39        "SampleAfterValue": "200003",
40        "BriefDescription": "MS decode starts"
41    },
42    {
43        "CollectPEBSRecord": "1",
44        "PublicDescription": "Counts the number of times the prediction (from the predecode cache) for instruction length is incorrect.",
45        "EventCode": "0xE9",
46        "Counter": "0,1,2,3",
47        "UMask": "0x1",
48        "EventName": "DECODE_RESTRICTION.PREDECODE_WRONG",
49        "SampleAfterValue": "200003",
50        "BriefDescription": "Decode restrictions due to predicting wrong instruction length"
51    }
52]