Commit 1b91a994 authored by Ian Rogers's avatar Ian Rogers Committed by Arnaldo Carvalho de Melo

perf vendor events intel: Refresh silvermont events

Update the silvermont events using the new tooling from:

  https://github.com/intel/perfmon

The events are unchanged but unused json values are removed. This
increases consistency across the json files.
Signed-off-by: default avatarIan Rogers <irogers@google.com>
Acked-by: default avatarKan Liang <kan.liang@linux.intel.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Caleb Biggers <caleb.biggers@intel.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: John Garry <john.g.garry@oracle.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Perry Taylor <perry.taylor@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Xing Zhengjun <zhengjun.xing@linux.intel.com>
Link: https://lore.kernel.org/r/20221215065510.1621979-17-irogers@google.comSigned-off-by: default avatarArnaldo Carvalho de Melo <acme@redhat.com>
parent 400dd489
[ [
{ {
"BriefDescription": "Stalls due to FP assists", "BriefDescription": "Stalls due to FP assists",
"Counter": "0,1",
"EventCode": "0xC3", "EventCode": "0xC3",
"EventName": "MACHINE_CLEARS.FP_ASSIST", "EventName": "MACHINE_CLEARS.FP_ASSIST",
"PublicDescription": "This event counts the number of times that pipeline stalled due to FP operations needing assists.", "PublicDescription": "This event counts the number of times that pipeline stalled due to FP operations needing assists.",
......
[ [
{ {
"BriefDescription": "Counts the number of baclears", "BriefDescription": "Counts the number of baclears",
"Counter": "0,1",
"EventCode": "0xE6", "EventCode": "0xE6",
"EventName": "BACLEARS.ALL", "EventName": "BACLEARS.ALL",
"PublicDescription": "The BACLEARS event counts the number of times the front end is resteered, mainly when the Branch Prediction Unit cannot provide a correct prediction and this is corrected by the Branch Address Calculator at the front end. The BACLEARS.ANY event counts the number of baclears for any type of branch.", "PublicDescription": "The BACLEARS event counts the number of times the front end is resteered, mainly when the Branch Prediction Unit cannot provide a correct prediction and this is corrected by the Branch Address Calculator at the front end. The BACLEARS.ANY event counts the number of baclears for any type of branch.",
...@@ -10,7 +9,6 @@ ...@@ -10,7 +9,6 @@
}, },
{ {
"BriefDescription": "Counts the number of JCC baclears", "BriefDescription": "Counts the number of JCC baclears",
"Counter": "0,1",
"EventCode": "0xE6", "EventCode": "0xE6",
"EventName": "BACLEARS.COND", "EventName": "BACLEARS.COND",
"PublicDescription": "The BACLEARS event counts the number of times the front end is resteered, mainly when the Branch Prediction Unit cannot provide a correct prediction and this is corrected by the Branch Address Calculator at the front end. The BACLEARS.COND event counts the number of JCC (Jump on Condtional Code) baclears.", "PublicDescription": "The BACLEARS event counts the number of times the front end is resteered, mainly when the Branch Prediction Unit cannot provide a correct prediction and this is corrected by the Branch Address Calculator at the front end. The BACLEARS.COND event counts the number of JCC (Jump on Condtional Code) baclears.",
...@@ -19,7 +17,6 @@ ...@@ -19,7 +17,6 @@
}, },
{ {
"BriefDescription": "Counts the number of RETURN baclears", "BriefDescription": "Counts the number of RETURN baclears",
"Counter": "0,1",
"EventCode": "0xE6", "EventCode": "0xE6",
"EventName": "BACLEARS.RETURN", "EventName": "BACLEARS.RETURN",
"PublicDescription": "The BACLEARS event counts the number of times the front end is resteered, mainly when the Branch Prediction Unit cannot provide a correct prediction and this is corrected by the Branch Address Calculator at the front end. The BACLEARS.RETURN event counts the number of RETURN baclears.", "PublicDescription": "The BACLEARS event counts the number of times the front end is resteered, mainly when the Branch Prediction Unit cannot provide a correct prediction and this is corrected by the Branch Address Calculator at the front end. The BACLEARS.RETURN event counts the number of RETURN baclears.",
...@@ -28,7 +25,6 @@ ...@@ -28,7 +25,6 @@
}, },
{ {
"BriefDescription": "Counts the number of times a decode restriction reduced the decode throughput due to wrong instruction length prediction", "BriefDescription": "Counts the number of times a decode restriction reduced the decode throughput due to wrong instruction length prediction",
"Counter": "0,1",
"EventCode": "0xE9", "EventCode": "0xE9",
"EventName": "DECODE_RESTRICTION.PREDECODE_WRONG", "EventName": "DECODE_RESTRICTION.PREDECODE_WRONG",
"PublicDescription": "Counts the number of times a decode restriction reduced the decode throughput due to wrong instruction length prediction.", "PublicDescription": "Counts the number of times a decode restriction reduced the decode throughput due to wrong instruction length prediction.",
...@@ -37,7 +33,6 @@ ...@@ -37,7 +33,6 @@
}, },
{ {
"BriefDescription": "Instruction fetches", "BriefDescription": "Instruction fetches",
"Counter": "0,1",
"EventCode": "0x80", "EventCode": "0x80",
"EventName": "ICACHE.ACCESSES", "EventName": "ICACHE.ACCESSES",
"PublicDescription": "This event counts all instruction fetches, not including most uncacheable\r\nfetches.", "PublicDescription": "This event counts all instruction fetches, not including most uncacheable\r\nfetches.",
...@@ -46,7 +41,6 @@ ...@@ -46,7 +41,6 @@
}, },
{ {
"BriefDescription": "Instruction fetches from Icache", "BriefDescription": "Instruction fetches from Icache",
"Counter": "0,1",
"EventCode": "0x80", "EventCode": "0x80",
"EventName": "ICACHE.HIT", "EventName": "ICACHE.HIT",
"PublicDescription": "This event counts all instruction fetches from the instruction cache.", "PublicDescription": "This event counts all instruction fetches from the instruction cache.",
...@@ -55,7 +49,6 @@ ...@@ -55,7 +49,6 @@
}, },
{ {
"BriefDescription": "Icache miss", "BriefDescription": "Icache miss",
"Counter": "0,1",
"EventCode": "0x80", "EventCode": "0x80",
"EventName": "ICACHE.MISSES", "EventName": "ICACHE.MISSES",
"PublicDescription": "This event counts all instruction fetches that miss the Instruction cache or produce memory requests. This includes uncacheable fetches. An instruction fetch miss is counted only once and not once for every cycle it is outstanding.", "PublicDescription": "This event counts all instruction fetches that miss the Instruction cache or produce memory requests. This includes uncacheable fetches. An instruction fetch miss is counted only once and not once for every cycle it is outstanding.",
...@@ -64,7 +57,6 @@ ...@@ -64,7 +57,6 @@
}, },
{ {
"BriefDescription": "Counts the number of times entered into a ucode flow in the FEC. Includes inserted flows due to front-end detected faults or assists. Speculative count.", "BriefDescription": "Counts the number of times entered into a ucode flow in the FEC. Includes inserted flows due to front-end detected faults or assists. Speculative count.",
"Counter": "0,1",
"EventCode": "0xE7", "EventCode": "0xE7",
"EventName": "MS_DECODED.MS_ENTRY", "EventName": "MS_DECODED.MS_ENTRY",
"PublicDescription": "Counts the number of times the MSROM starts a flow of UOPS. It does not count every time a UOP is read from the microcode ROM. 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. The event will count MSROM startups for UOPS that are speculative, and subsequently cleared by branch mispredict or machine clear. Background: UOPS are produced by two mechanisms. Either they are generated by hardware that decodes instructions into UOPS, or they are delivered by a ROM (called the MSROM) that holds UOPS associated with a specific instruction. MSROM UOPS might also be delivered in response to some condition such as a fault or other exceptional condition. This event is an excellent mechanism for detecting instructions that require the use of MSROM instructions.", "PublicDescription": "Counts the number of times the MSROM starts a flow of UOPS. It does not count every time a UOP is read from the microcode ROM. 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. The event will count MSROM startups for UOPS that are speculative, and subsequently cleared by branch mispredict or machine clear. Background: UOPS are produced by two mechanisms. Either they are generated by hardware that decodes instructions into UOPS, or they are delivered by a ROM (called the MSROM) that holds UOPS associated with a specific instruction. MSROM UOPS might also be delivered in response to some condition such as a fault or other exceptional condition. This event is an excellent mechanism for detecting instructions that require the use of MSROM instructions.",
......
[ [
{ {
"BriefDescription": "Stalls due to Memory ordering", "BriefDescription": "Stalls due to Memory ordering",
"Counter": "0,1",
"EventCode": "0xC3", "EventCode": "0xC3",
"EventName": "MACHINE_CLEARS.MEMORY_ORDERING", "EventName": "MACHINE_CLEARS.MEMORY_ORDERING",
"PublicDescription": "This event counts the number of times that pipeline was cleared due to memory ordering issues.", "PublicDescription": "This event counts the number of times that pipeline was cleared due to memory ordering issues.",
......
[ [
{ {
"BriefDescription": "Cycles code-fetch stalled due to any reason.", "BriefDescription": "Cycles code-fetch stalled due to any reason.",
"Counter": "0,1",
"EventCode": "0x86", "EventCode": "0x86",
"EventName": "FETCH_STALL.ALL", "EventName": "FETCH_STALL.ALL",
"PublicDescription": "Counts cycles that fetch is stalled due to any reason. That is, the decoder queue is able to accept bytes, but the fetch unit is unable to provide bytes. This will include cycles due to an ITLB miss, ICache miss and other events.", "PublicDescription": "Counts cycles that fetch is stalled due to any reason. That is, the decoder queue is able to accept bytes, but the fetch unit is unable to provide bytes. This will include cycles due to an ITLB miss, ICache miss and other events.",
...@@ -10,7 +9,6 @@ ...@@ -10,7 +9,6 @@
}, },
{ {
"BriefDescription": "Cycles code-fetch stalled due to an outstanding ITLB miss.", "BriefDescription": "Cycles code-fetch stalled due to an outstanding ITLB miss.",
"Counter": "0,1",
"EventCode": "0x86", "EventCode": "0x86",
"EventName": "FETCH_STALL.ITLB_FILL_PENDING_CYCLES", "EventName": "FETCH_STALL.ITLB_FILL_PENDING_CYCLES",
"PublicDescription": "Counts cycles that fetch is stalled due to an outstanding ITLB miss. That is, the decoder queue is able to accept bytes, but the fetch unit is unable to provide bytes due to an ITLB miss. Note: this event is not the same as page walk cycles to retrieve an instruction translation.", "PublicDescription": "Counts cycles that fetch is stalled due to an outstanding ITLB miss. That is, the decoder queue is able to accept bytes, but the fetch unit is unable to provide bytes due to an ITLB miss. Note: this event is not the same as page walk cycles to retrieve an instruction translation.",
......
[ [
{ {
"BriefDescription": "Loads missed DTLB", "BriefDescription": "Loads missed DTLB",
"Counter": "0,1",
"EventCode": "0x04", "EventCode": "0x04",
"EventName": "MEM_UOPS_RETIRED.DTLB_MISS_LOADS", "EventName": "MEM_UOPS_RETIRED.DTLB_MISS_LOADS",
"PEBS": "1", "PEBS": "1",
...@@ -11,7 +10,6 @@ ...@@ -11,7 +10,6 @@
}, },
{ {
"BriefDescription": "Total cycles for all the page walks. (I-side and D-side)", "BriefDescription": "Total cycles for all the page walks. (I-side and D-side)",
"Counter": "0,1",
"EventCode": "0x05", "EventCode": "0x05",
"EventName": "PAGE_WALKS.CYCLES", "EventName": "PAGE_WALKS.CYCLES",
"PublicDescription": "This event counts every cycle when a data (D) page walk or instruction (I) page walk is in progress. Since a pagewalk implies a TLB miss, the approximate cost of a TLB miss can be determined from this event.", "PublicDescription": "This event counts every cycle when a data (D) page walk or instruction (I) page walk is in progress. Since a pagewalk implies a TLB miss, the approximate cost of a TLB miss can be determined from this event.",
...@@ -20,7 +18,6 @@ ...@@ -20,7 +18,6 @@
}, },
{ {
"BriefDescription": "Duration of D-side page-walks in core cycles", "BriefDescription": "Duration of D-side page-walks in core cycles",
"Counter": "0,1",
"EventCode": "0x05", "EventCode": "0x05",
"EventName": "PAGE_WALKS.D_SIDE_CYCLES", "EventName": "PAGE_WALKS.D_SIDE_CYCLES",
"PublicDescription": "This event counts every cycle when a D-side (walks due to a load) page walk is in progress. Page walk duration divided by number of page walks is the average duration of page-walks.", "PublicDescription": "This event counts every cycle when a D-side (walks due to a load) page walk is in progress. Page walk duration divided by number of page walks is the average duration of page-walks.",
...@@ -29,7 +26,6 @@ ...@@ -29,7 +26,6 @@
}, },
{ {
"BriefDescription": "D-side page-walks", "BriefDescription": "D-side page-walks",
"Counter": "0,1",
"EdgeDetect": "1", "EdgeDetect": "1",
"EventCode": "0x05", "EventCode": "0x05",
"EventName": "PAGE_WALKS.D_SIDE_WALKS", "EventName": "PAGE_WALKS.D_SIDE_WALKS",
...@@ -39,7 +35,6 @@ ...@@ -39,7 +35,6 @@
}, },
{ {
"BriefDescription": "Duration of I-side page-walks in core cycles", "BriefDescription": "Duration of I-side page-walks in core cycles",
"Counter": "0,1",
"EventCode": "0x05", "EventCode": "0x05",
"EventName": "PAGE_WALKS.I_SIDE_CYCLES", "EventName": "PAGE_WALKS.I_SIDE_CYCLES",
"PublicDescription": "This event counts every cycle when a I-side (walks due to an instruction fetch) page walk is in progress. Page walk duration divided by number of page walks is the average duration of page-walks.", "PublicDescription": "This event counts every cycle when a I-side (walks due to an instruction fetch) page walk is in progress. Page walk duration divided by number of page walks is the average duration of page-walks.",
...@@ -48,7 +43,6 @@ ...@@ -48,7 +43,6 @@
}, },
{ {
"BriefDescription": "I-side page-walks", "BriefDescription": "I-side page-walks",
"Counter": "0,1",
"EdgeDetect": "1", "EdgeDetect": "1",
"EventCode": "0x05", "EventCode": "0x05",
"EventName": "PAGE_WALKS.I_SIDE_WALKS", "EventName": "PAGE_WALKS.I_SIDE_WALKS",
...@@ -58,7 +52,6 @@ ...@@ -58,7 +52,6 @@
}, },
{ {
"BriefDescription": "Total page walks that are completed (I-side and D-side)", "BriefDescription": "Total page walks that are completed (I-side and D-side)",
"Counter": "0,1",
"EdgeDetect": "1", "EdgeDetect": "1",
"EventCode": "0x05", "EventCode": "0x05",
"EventName": "PAGE_WALKS.WALKS", "EventName": "PAGE_WALKS.WALKS",
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment