From: Chun-Tse Shao <ctshao@google.com>
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org
Cc: mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, dapeng1.mi@linux.intel.com,
thomas.falcon@intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, Chun-Tse Shao <ctshao@google.com>
Subject: [PATCH v1 3/3] perf vendor events intel: Update novalake events from 1.04 to 1.05
Date: Wed, 18 Nov 2026 13:26:55 -0800 [thread overview]
Message-ID: <20261118212655.2262601-4-ctshao@google.com> (raw)
In-Reply-To: <20261118212655.2262601-1-ctshao@google.com>
The updated events were published in:
https://github.com/intel/perfmon/commit/409ce6f3950c46f6cd3deac31b93d66a6ae82d6e
Signed-off-by: Chun-Tse Shao <ctshao@google.com>
Assisted-by: Gemini:gemini-4-carbon
---
tools/perf/pmu-events/arch/x86/mapfile.csv | 2 +-
.../pmu-events/arch/x86/novalake/cache.json | 13 ++-
.../pmu-events/arch/x86/novalake/counter.json | 5 ++
.../arch/x86/novalake/floating-point.json | 4 +-
.../pmu-events/arch/x86/novalake/memory.json | 39 ++++++++-
.../pmu-events/arch/x86/novalake/other.json | 84 +++++++++++++++++++
.../arch/x86/novalake/pipeline.json | 75 +++++++++++++++++
.../arch/x86/novalake/uncore-cache.json | 11 +++
8 files changed, 227 insertions(+), 6 deletions(-)
create mode 100644 tools/perf/pmu-events/arch/x86/novalake/uncore-cache.json
diff --git a/tools/perf/pmu-events/arch/x86/mapfile.csv b/tools/perf/pmu-events/arch/x86/mapfile.csv
index 5e6bff382c23..7b88b9fad945 100644
--- a/tools/perf/pmu-events/arch/x86/mapfile.csv
+++ b/tools/perf/pmu-events/arch/x86/mapfile.csv
@@ -27,7 +27,7 @@ GenuineIntel-6-BD,v1.27,lunarlake,core
GenuineIntel-6-(AA|AC|B5),v1.23,meteorlake,core
GenuineIntel-6-1[AEF],v4,nehalemep,core
GenuineIntel-6-2E,v4,nehalemex,core
-GenuineIntel-18-[13],v1.04,novalake,core
+GenuineIntel-18-[13],v1.05,novalake,core
GenuineIntel-6-(CC|D5|E5),v1.08,pantherlake,core
GenuineIntel-6-A7,v1.06,rocketlake,core
GenuineIntel-6-2A,v19,sandybridge,core
diff --git a/tools/perf/pmu-events/arch/x86/novalake/cache.json b/tools/perf/pmu-events/arch/x86/novalake/cache.json
index e8d416ffd421..808858f1871e 100644
--- a/tools/perf/pmu-events/arch/x86/novalake/cache.json
+++ b/tools/perf/pmu-events/arch/x86/novalake/cache.json
@@ -249,7 +249,7 @@
"Unit": "cpu_core"
},
{
- "BriefDescription": "L2_REQUEST.RFO_HIT_XSNP_HIT_FWD",
+ "BriefDescription": "L2_REQUEST.RFO_HIT_XSNP_HIT_FWD [This event is alias to L2_RQSTS.RFO_HIT_XSNP_HIT_FWD]",
"Counter": "0,1,2,3,4,5,6,7",
"EventCode": "0x24",
"EventName": "L2_REQUEST.RFO_HIT_XSNP_HIT_FWD",
@@ -377,6 +377,15 @@
"UMask": "0x42",
"Unit": "cpu_core"
},
+ {
+ "BriefDescription": "L2_RQSTS.RFO_HIT_XSNP_HIT_FWD [This event is alias to L2_REQUEST.RFO_HIT_XSNP_HIT_FWD]",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0x24",
+ "EventName": "L2_RQSTS.RFO_HIT_XSNP_HIT_FWD",
+ "SampleAfterValue": "200003",
+ "UMask": "0x2002",
+ "Unit": "cpu_core"
+ },
{
"BriefDescription": "RFO requests that miss L2 cache [This event is alias to L2_REQUEST.RFO_MISS]",
"Counter": "0,1,2,3,4,5,6,7",
@@ -1174,7 +1183,7 @@
"EventCode": "0x2c",
"EventName": "SQ_MISC.BUS_LOCK",
"PublicDescription": "Counts the more expensive bus lock needed to enforce cache coherency for certain memory accesses that need to be done atomically. Can be created by issuing an atomic instruction (via the LOCK prefix) which causes a cache line split or accesses uncacheable memory.",
- "SampleAfterValue": "100003",
+ "SampleAfterValue": "503",
"UMask": "0x10",
"Unit": "cpu_core"
},
diff --git a/tools/perf/pmu-events/arch/x86/novalake/counter.json b/tools/perf/pmu-events/arch/x86/novalake/counter.json
index 6cdc63552c67..0ab92c0013b6 100644
--- a/tools/perf/pmu-events/arch/x86/novalake/counter.json
+++ b/tools/perf/pmu-events/arch/x86/novalake/counter.json
@@ -13,5 +13,10 @@
"Unit": "iMC",
"CountersNumFixed": "0",
"CountersNumGeneric": "5"
+ },
+ {
+ "Unit": "CBOX",
+ "CountersNumFixed": "0",
+ "CountersNumGeneric": 2
}
]
\ No newline at end of file
diff --git a/tools/perf/pmu-events/arch/x86/novalake/floating-point.json b/tools/perf/pmu-events/arch/x86/novalake/floating-point.json
index 455f752a746d..f60bf04b87af 100644
--- a/tools/perf/pmu-events/arch/x86/novalake/floating-point.json
+++ b/tools/perf/pmu-events/arch/x86/novalake/floating-point.json
@@ -359,7 +359,7 @@
"EventName": "FP_ARITH_OPS_RETIRED.SCALAR",
"PublicDescription": "Number of SSE/AVX computational scalar single precision and double precision floating-point instructions retired; some instructions will count twice as noted below. Each count represents 1 computational operation. Applies to SSE* and AVX* scalar single precision floating-point instructions: ADD SUB MUL DIV MIN MAX SQRT RSQRT RCP FM(N)ADD/SUB. FM(N)ADD/SUB instructions count twice as they perform 2 calculations per element. The DAZ and FTZ flags in the MXCSR register need to be set when using these events.",
"SampleAfterValue": "1000003",
- "UMask": "0x3",
+ "UMask": "0x303",
"Unit": "cpu_core"
},
{
@@ -389,7 +389,7 @@
"EventName": "FP_ARITH_OPS_RETIRED.VECTOR",
"PublicDescription": "Number of any Vector retired FP arithmetic instructions. The DAZ and FTZ flags in the MXCSR register need to be set when using these events.",
"SampleAfterValue": "1000003",
- "UMask": "0x3c",
+ "UMask": "0x1cfc",
"Unit": "cpu_core"
},
{
diff --git a/tools/perf/pmu-events/arch/x86/novalake/memory.json b/tools/perf/pmu-events/arch/x86/novalake/memory.json
index 618bcb7cb3e1..8e7488a88e77 100644
--- a/tools/perf/pmu-events/arch/x86/novalake/memory.json
+++ b/tools/perf/pmu-events/arch/x86/novalake/memory.json
@@ -132,7 +132,7 @@
"Counter": "0,1,2,3,4,5,6,7",
"EventCode": "0xc3",
"EventName": "MACHINE_CLEARS.MEMORY_ORDERING",
- "PublicDescription": "Counts the number of Machine Clears detected dye to memory ordering. Memory Ordering Machine Clears may apply when a memory read may not conform to the memory ordering rules of the x86 architecture",
+ "PublicDescription": "Counts the number of Machine Clears detected due to memory ordering. Memory Ordering Machine Clears may apply when a memory read may not conform to the memory ordering rules of the x86 architecture",
"SampleAfterValue": "100003",
"UMask": "0x2",
"Unit": "cpu_core"
@@ -155,6 +155,18 @@
"UMask": "0x48",
"Unit": "cpu_core"
},
+ {
+ "BriefDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than any number of cycles.",
+ "Counter": "2,3,4,5,6,7",
+ "Data_LA": "1",
+ "EventCode": "0xcd",
+ "EventName": "MEM_TRANS_RETIRED.LOAD_LATENCY_GT",
+ "MSRIndex": "0x3F6",
+ "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than any number of cycles. Reported latency may be longer than just the memory latency. Available PDIST counters: 0,1",
+ "SampleAfterValue": "100003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
{
"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.",
"Counter": "2,3,4,5,6,7",
@@ -194,6 +206,19 @@
"UMask": "0x1",
"Unit": "cpu_core"
},
+ {
+ "BriefDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 2 cycles.",
+ "Counter": "2,3,4,5,6,7",
+ "Data_LA": "1",
+ "EventCode": "0xcd",
+ "EventName": "MEM_TRANS_RETIRED.LOAD_LATENCY_GT_2",
+ "MSRIndex": "0x3F6",
+ "MSRValue": "0x2",
+ "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 2 cycles. Reported latency may be longer than just the memory latency. Available PDIST counters: 0,1",
+ "SampleAfterValue": "100003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
{
"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 2048 cycles.",
"Counter": "2,3,4,5,6,7",
@@ -308,6 +333,18 @@
"UMask": "0x1",
"Unit": "cpu_core"
},
+ {
+ "BriefDescription": "OMR.DEMAND_RFO.L3_MISS",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0x2A",
+ "EventName": "OMR.DEMAND_RFO.L3_MISS",
+ "MSRIndex": "0x3E0,0x3E1,0x3E2,0x3E3",
+ "MSRValue": "0xFF03F000000002",
+ "PublicDescription": "OMR.DEMAND_RFO.L3_MISS Available PDIST counters: 0",
+ "SampleAfterValue": "100003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
{
"BriefDescription": "OMR.READS_TO_CORE.L3_MISS",
"Counter": "0,1,2,3,4,5,6,7",
diff --git a/tools/perf/pmu-events/arch/x86/novalake/other.json b/tools/perf/pmu-events/arch/x86/novalake/other.json
index 19932b311486..1c0d4e729e1f 100644
--- a/tools/perf/pmu-events/arch/x86/novalake/other.json
+++ b/tools/perf/pmu-events/arch/x86/novalake/other.json
@@ -175,6 +175,54 @@
"UMask": "0x1",
"Unit": "cpu_core"
},
+ {
+ "BriefDescription": "OMR.DEMAND_DATA_RD.L3_SAME_CBB.HIT",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0x2A",
+ "EventName": "OMR.DEMAND_DATA_RD.L3_SAME_CBB.HIT",
+ "MSRIndex": "0x3E0,0x3E1,0x3E2,0x3E3",
+ "MSRValue": "0xED000400000001",
+ "PublicDescription": "OMR.DEMAND_DATA_RD.L3_SAME_CBB.HIT Available PDIST counters: 0",
+ "SampleAfterValue": "100003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
+ {
+ "BriefDescription": "OMR.DEMAND_DATA_RD.L3_SAME_CBB.HIT.SNP_HIT_NO_FWD",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0x2A",
+ "EventName": "OMR.DEMAND_DATA_RD.L3_SAME_CBB.HIT.SNP_HIT_NO_FWD",
+ "MSRIndex": "0x3E0,0x3E1,0x3E2,0x3E3",
+ "MSRValue": "0x4D000400000001",
+ "PublicDescription": "OMR.DEMAND_DATA_RD.L3_SAME_CBB.HIT.SNP_HIT_NO_FWD Available PDIST counters: 0",
+ "SampleAfterValue": "100003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
+ {
+ "BriefDescription": "OMR.DEMAND_DATA_RD.L3_SAME_CBB.HITESF",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0x2A",
+ "EventName": "OMR.DEMAND_DATA_RD.L3_SAME_CBB.HITESF",
+ "MSRIndex": "0x3E0,0x3E1,0x3E2,0x3E3",
+ "MSRValue": "0xE5000400000001",
+ "PublicDescription": "OMR.DEMAND_DATA_RD.L3_SAME_CBB.HITESF Available PDIST counters: 0",
+ "SampleAfterValue": "100003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
+ {
+ "BriefDescription": "OMR.DEMAND_DATA_RD.L3_SAME_CBB.HITM",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0x2A",
+ "EventName": "OMR.DEMAND_DATA_RD.L3_SAME_CBB.HITM",
+ "MSRIndex": "0x3E0,0x3E1,0x3E2,0x3E3",
+ "MSRValue": "0xE9000400000001",
+ "PublicDescription": "OMR.DEMAND_DATA_RD.L3_SAME_CBB.HITM Available PDIST counters: 0",
+ "SampleAfterValue": "100003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
{
"BriefDescription": "OMR.DEMAND_DATA_RD.MEM_REGION_0",
"Counter": "0,1,2,3,4,5,6,7",
@@ -199,6 +247,42 @@
"UMask": "0x1",
"Unit": "cpu_core"
},
+ {
+ "BriefDescription": "OMR.DEMAND_RFO.ANY_RESPONSE",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0x2A",
+ "EventName": "OMR.DEMAND_RFO.ANY_RESPONSE",
+ "MSRIndex": "0x3E0,0x3E1,0x3E2,0x3E3",
+ "MSRValue": "0x4000000000000002",
+ "PublicDescription": "OMR.DEMAND_RFO.ANY_RESPONSE Available PDIST counters: 0",
+ "SampleAfterValue": "100003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
+ {
+ "BriefDescription": "OMR.DEMAND_RFO.L3_SAME_CBB.HITM",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0x2A",
+ "EventName": "OMR.DEMAND_RFO.L3_SAME_CBB.HITM",
+ "MSRIndex": "0x3E0,0x3E1,0x3E2,0x3E3",
+ "MSRValue": "0xE9000400000002",
+ "PublicDescription": "OMR.DEMAND_RFO.L3_SAME_CBB.HITM Available PDIST counters: 0",
+ "SampleAfterValue": "100003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
+ {
+ "BriefDescription": "OMR.MODIFIED_WRITE.ANY_RESPONSE",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0x2A",
+ "EventName": "OMR.MODIFIED_WRITE.ANY_RESPONSE",
+ "MSRIndex": "0x3E0,0x3E1,0x3E2,0x3E3",
+ "MSRValue": "0x4000000000000808",
+ "PublicDescription": "OMR.MODIFIED_WRITE.ANY_RESPONSE Available PDIST counters: 0",
+ "SampleAfterValue": "100003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
{
"BriefDescription": "OMR.READS_TO_CORE.ANY_MEMORY",
"Counter": "0,1,2,3,4,5,6,7",
diff --git a/tools/perf/pmu-events/arch/x86/novalake/pipeline.json b/tools/perf/pmu-events/arch/x86/novalake/pipeline.json
index 8b2e1ed2331d..382d08f79416 100644
--- a/tools/perf/pmu-events/arch/x86/novalake/pipeline.json
+++ b/tools/perf/pmu-events/arch/x86/novalake/pipeline.json
@@ -2219,6 +2219,16 @@
"UMask": "0x1",
"Unit": "cpu_core"
},
+ {
+ "BriefDescription": "Cycles where at least 10 uops was executed per-thread",
+ "Counter": "3",
+ "CounterMask": "10",
+ "EventCode": "0xb1",
+ "EventName": "UOPS_EXECUTED.CYCLES_GE_10",
+ "SampleAfterValue": "2000003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
{
"BriefDescription": "Cycles where at least 2 uops were executed per-thread",
"Counter": "3",
@@ -2252,6 +2262,26 @@
"UMask": "0x1",
"Unit": "cpu_core"
},
+ {
+ "BriefDescription": "Cycles where at least 6 uops was executed per-thread",
+ "Counter": "3",
+ "CounterMask": "6",
+ "EventCode": "0xb1",
+ "EventName": "UOPS_EXECUTED.CYCLES_GE_6",
+ "SampleAfterValue": "2000003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
+ {
+ "BriefDescription": "Cycles where at least 8 uops was executed per-thread",
+ "Counter": "3",
+ "CounterMask": "8",
+ "EventCode": "0xb1",
+ "EventName": "UOPS_EXECUTED.CYCLES_GE_8",
+ "SampleAfterValue": "2000003",
+ "UMask": "0x1",
+ "Unit": "cpu_core"
+ },
{
"BriefDescription": "Counts number of cycles no uops were dispatched to be executed on this thread.",
"Counter": "3",
@@ -2464,5 +2494,50 @@
"SampleAfterValue": "1000003",
"UMask": "0x1",
"Unit": "cpu_core"
+ },
+ {
+ "BriefDescription": "Counts number of vector uops dispatched on VEC1",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0xb4",
+ "EventName": "VEC_DISPATCHED.V1",
+ "SampleAfterValue": "1000003",
+ "UMask": "0x2",
+ "Unit": "cpu_core"
+ },
+ {
+ "BriefDescription": "Counts number of vector uops dispatched on VEC2",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0xb4",
+ "EventName": "VEC_DISPATCHED.V2",
+ "SampleAfterValue": "1000003",
+ "UMask": "0x4",
+ "Unit": "cpu_core"
+ },
+ {
+ "BriefDescription": "Counts number of vector uops dispatched on VEC3",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0xb4",
+ "EventName": "VEC_DISPATCHED.V3",
+ "SampleAfterValue": "1000003",
+ "UMask": "0x8",
+ "Unit": "cpu_core"
+ },
+ {
+ "BriefDescription": "Counts number of vector uops dispatched on VEC4",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0xb4",
+ "EventName": "VEC_DISPATCHED.V4",
+ "SampleAfterValue": "1000003",
+ "UMask": "0x10",
+ "Unit": "cpu_core"
+ },
+ {
+ "BriefDescription": "Counts number of vector uops dispatched on VEC5",
+ "Counter": "0,1,2,3,4,5,6,7",
+ "EventCode": "0xb4",
+ "EventName": "VEC_DISPATCHED.V5",
+ "SampleAfterValue": "1000003",
+ "UMask": "0x20",
+ "Unit": "cpu_core"
}
]
diff --git a/tools/perf/pmu-events/arch/x86/novalake/uncore-cache.json b/tools/perf/pmu-events/arch/x86/novalake/uncore-cache.json
new file mode 100644
index 000000000000..a71772c6bb82
--- /dev/null
+++ b/tools/perf/pmu-events/arch/x86/novalake/uncore-cache.json
@@ -0,0 +1,11 @@
+[
+ {
+ "BriefDescription": "Counts UCLK ungated cycles.",
+ "Counter": "0,1",
+ "EventCode": "0x2d",
+ "EventName": "UNC_CBO_SBO_UCLK_CYCLES.UNGATED",
+ "PerPkg": "1",
+ "UMask": "0x2",
+ "Unit": "CBOX"
+ }
+]
--
2.56.1.708.g77570a6a1d-goog
prev parent reply other threads:[~2026-11-18 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 21:26 [PATCH v1 0/3] perf vendor events intel: update Chun-Tse Shao
2026-11-18 21:26 ` [PATCH v1 1/3] perf vendor events intel: Add diamondrapids v1.00 events Chun-Tse Shao
2026-11-18 21:26 ` [PATCH v1 2/3] perf vendor events intel: Update lunarlake events from 1.26 to 1.27 Chun-Tse Shao
2026-11-18 21:26 ` Chun-Tse Shao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261118212655.2262601-4-ctshao@google.com \
--to=ctshao@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=thomas.falcon@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®