From: "Chen, Zide" <zide.chen@intel.com>
To: Dapeng Mi <dapeng1.mi@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
Eranian Stephane <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Dapeng Mi <dapeng1.mi@intel.com>,
Falcon Thomas <thomas.falcon@intel.com>,
Xudong Hao <xudong.hao@intel.com>
Subject: Re: [PATCH 02/11] perf/x86/intel: Update event constraints and cache_extra_regs[] for SPR
Date: Tue, 19 May 2026 17:25:27 -0500 [thread overview]
Message-ID: <9bcfb336-00f4-4f26-bca1-fa08d74a6828@intel.com> (raw)
In-Reply-To: <20260515061143.338553-3-dapeng1.mi@linux.intel.com>
On 5/15/2026 11:11 PM, Dapeng Mi wrote:
> Update perf hard-coded event constraints and cache_extra_regs[] for
> Sapphire rapids according to the latest SPR perfmon events (v1.39).
>
> Emerald Rapids (EMR) and Granite Rapids (GNR) share exactly same event
> constraints and extra MSR values with SPR. No extra changes are needed
> for EMR and GNR.
>
> Please note the change could temporarily impact other platforms which
> share the hard coded data structures, but it would be fixed in
> subsequent patches soon.
This may make bisection difficult. Would it be possible to reorder the
patches to avoid this? For example, moving patch 6/11 ahead of this
patch to avoid impacting Lunar Lake.
> SPR perfmon events:
> https://github.com/intel/perfmon/blob/main/SPR/events/sapphirerapids_core.json
>
> Signed-off-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
> ---
> arch/x86/events/intel/core.c | 23 ++++++++++++++---------
> 1 file changed, 14 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> index 1390d1da985b..b3ccc785a4f6 100644
> --- a/arch/x86/events/intel/core.c
> +++ b/arch/x86/events/intel/core.c
> @@ -356,11 +356,12 @@ static struct extra_reg intel_glc_extra_regs[] __read_mostly = {
>
> static struct event_constraint intel_glc_event_constraints[] = {
> FIXED_EVENT_CONSTRAINT(0x00c0, 0), /* INST_RETIRED.ANY */
> - FIXED_EVENT_CONSTRAINT(0x0100, 0), /* INST_RETIRED.PREC_DIST */
> + FIXED_EVENT_CONSTRAINT(0x0100, 0), /* pseudo INST_RETIRED.ANY */
> FIXED_EVENT_CONSTRAINT(0x003c, 1), /* CPU_CLK_UNHALTED.CORE */
> - FIXED_EVENT_CONSTRAINT(0x0300, 2), /* CPU_CLK_UNHALTED.REF */
> + FIXED_EVENT_CONSTRAINT(0x0200, 1), /* pseudo CPU_CLK_UNHALTED.THREAD */
> + FIXED_EVENT_CONSTRAINT(0x0300, 2), /* pseudo CPU_CLK_UNHALTED.REF_TSC */
> FIXED_EVENT_CONSTRAINT(0x013c, 2), /* CPU_CLK_UNHALTED.REF_TSC_P */
> - FIXED_EVENT_CONSTRAINT(0x0400, 3), /* SLOTS */
> + FIXED_EVENT_CONSTRAINT(0x0400, 3), /* pseudo TOPDOWN.SLOTS */
> METRIC_EVENT_CONSTRAINT(INTEL_TD_METRIC_RETIRING, 0),
> METRIC_EVENT_CONSTRAINT(INTEL_TD_METRIC_BAD_SPEC, 1),
> METRIC_EVENT_CONSTRAINT(INTEL_TD_METRIC_FE_BOUND, 2),
> @@ -380,9 +381,13 @@ static struct event_constraint intel_glc_event_constraints[] = {
>
> INTEL_UEVENT_CONSTRAINT(0x01a3, 0xf),
> INTEL_UEVENT_CONSTRAINT(0x02a3, 0xf),
> + INTEL_UEVENT_CONSTRAINT(0x05a3, 0xf),
> + INTEL_UEVENT_CONSTRAINT(0x06a3, 0xf),
> INTEL_UEVENT_CONSTRAINT(0x08a3, 0xf),
> + INTEL_UEVENT_CONSTRAINT(0x0ca3, 0xf),
> INTEL_UEVENT_CONSTRAINT(0x04a4, 0x1),
> INTEL_UEVENT_CONSTRAINT(0x08a4, 0x1),
> + INTEL_UEVENT_CONSTRAINT(0x01cd, 0xfe),
> INTEL_UEVENT_CONSTRAINT(0x02cd, 0x1),
> INTEL_EVENT_CONSTRAINT(0xce, 0x1),
> INTEL_EVENT_CONSTRAINT_RANGE(0xd0, 0xdf, 0xf),
> @@ -714,18 +719,18 @@ static __initconst const u64 glc_hw_cache_extra_regs
> {
> [ C(LL ) ] = {
> [ C(OP_READ) ] = {
> - [ C(RESULT_ACCESS) ] = 0x10001,
> - [ C(RESULT_MISS) ] = 0x3fbfc00001,
> + [ C(RESULT_ACCESS) ] = 0x10001, /* OCR.DEMAND_DATA_RD.ANY_RESPONSE */
> + [ C(RESULT_MISS) ] = 0x3fbfc00001, /* OCR.DEMAND_DATA_RD.L3_MISS */
> },
> [ C(OP_WRITE) ] = {
> - [ C(RESULT_ACCESS) ] = 0x3f3ffc0002,
> - [ C(RESULT_MISS) ] = 0x3f3fc00002,
> + [ C(RESULT_ACCESS) ] = 0x3f3ffc0002, /* OCR.DEMAND_RFO.ANY_RESPONSE */
> + [ C(RESULT_MISS) ] = 0x3f3fc00002, /* OCR.DEMAND_RFO.L3_MISS */
> },
> },
> [ C(NODE) ] = {
> [ C(OP_READ) ] = {
> - [ C(RESULT_ACCESS) ] = 0x10c000001,
> - [ C(RESULT_MISS) ] = 0x3fb3000001,
> + [ C(RESULT_ACCESS) ] = 0x104000001, /* OCR.DEMAND_DATA_RD.LOCAL_DRAM */
> + [ C(RESULT_MISS) ] = 0x730000001, /* OCR.DEMAND_DATA_RD.REMOTE_DRAM */
> },
> },
> };
next prev parent reply other threads:[~2026-05-19 22:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 6:11 [PATCH 00/11] perf/x86/intel: Fix inaccurate hard-coded event configurations Dapeng Mi
2026-05-15 6:11 ` [PATCH 01/11] perf/x86/intel: Update event constraints and cache_extra_regs[] for ICX Dapeng Mi
2026-05-19 22:19 ` Chen, Zide
2026-05-20 1:10 ` Mi, Dapeng
2026-05-20 8:33 ` [tip: perf/core] perf/x86/intel: Update event constraints and cache_extra_regsfor ICX tip-bot2 for Dapeng Mi
2026-05-15 6:11 ` [PATCH 02/11] perf/x86/intel: Update event constraints and cache_extra_regs[] for SPR Dapeng Mi
2026-05-19 22:25 ` Chen, Zide [this message]
2026-05-20 2:08 ` Mi, Dapeng
2026-05-20 8:33 ` [tip: perf/core] perf/x86/intel: Update event constraints and cache_extra_regsfor SPR tip-bot2 for Dapeng Mi
2026-05-15 6:11 ` [PATCH 03/11] perf/x86/intel: Update event constraints for DMR Dapeng Mi
2026-05-19 22:19 ` Chen, Zide
2026-05-20 8:33 ` [tip: perf/core] " tip-bot2 for Dapeng Mi
2026-05-15 6:11 ` [PATCH 04/11] perf/x86/intel: Update event constraints and cache_extra_regs[] for ADL Dapeng Mi
2026-05-19 22:26 ` Chen, Zide
2026-05-20 8:33 ` [tip: perf/core] perf/x86/intel: Update event constraints and cache_extra_regsfor ADL tip-bot2 for Dapeng Mi
2026-05-15 6:11 ` [PATCH 05/11] perf/x86/intel: Update event constraints and cache_extra_regs[] for MTL Dapeng Mi
2026-05-20 8:33 ` [tip: perf/core] perf/x86/intel: Update event constraints and cache_extra_regsfor MTL tip-bot2 for Dapeng Mi
2026-05-15 6:11 ` [PATCH 06/11] perf/x86/intel: Update event constraints and cache_extra_regs[] for LNL Dapeng Mi
2026-05-20 8:33 ` [tip: perf/core] perf/x86/intel: Update event constraints and cache_extra_regsfor LNL tip-bot2 for Dapeng Mi
2026-05-15 6:11 ` [PATCH 07/11] perf/x86/intel: Update event constraints and cache_extra_regs[] for ARL Dapeng Mi
2026-05-20 8:33 ` [tip: perf/core] perf/x86/intel: Update event constraints and cache_extra_regsfor ARL tip-bot2 for Dapeng Mi
2026-05-15 6:11 ` [PATCH 08/11] perf/x86/intel: Update event constraints for PTL Dapeng Mi
2026-05-20 8:33 ` [tip: perf/core] " tip-bot2 for Dapeng Mi
2026-05-15 6:11 ` [PATCH 09/11] perf/x86/intel: Update event constraints and cache_extra_regs[] for NVL Dapeng Mi
2026-05-20 8:33 ` [tip: perf/core] perf/x86/intel: Update event constraints and cache_extra_regsfor NVL tip-bot2 for Dapeng Mi
2026-05-15 6:11 ` [PATCH 10/11] perf/x86/intel: Update event constraints and cache_extra_regs[] for SRF Dapeng Mi
2026-05-19 22:23 ` Chen, Zide
2026-05-20 2:11 ` Mi, Dapeng
2026-05-20 8:33 ` [tip: perf/core] perf/x86/intel: Update event constraints and cache_extra_regsfor SRF tip-bot2 for Dapeng Mi
2026-05-15 6:11 ` [PATCH 11/11] perf/x86/intel: Update event constraints and cache_extra_regs[] for CWF Dapeng Mi
2026-05-20 8:33 ` [tip: perf/core] perf/x86/intel: Update event constraints and cache_extra_regsfor CWF tip-bot2 for Dapeng Mi
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=9bcfb336-00f4-4f26-bca1-fa08d74a6828@intel.com \
--to=zide.chen@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=thomas.falcon@intel.com \
--cc=xudong.hao@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
Powered by JetHome