]> www.infradead.org Git - users/jedix/linux-maple.git/commit
perf/x86/intel: Add a distinct name for Granite Rapids
authorKan Liang <kan.liang@linux.intel.com>
Mon, 8 Jul 2024 19:33:35 +0000 (12:33 -0700)
committerPeter Zijlstra <peterz@infradead.org>
Tue, 9 Jul 2024 11:26:39 +0000 (13:26 +0200)
commitfa0c1c9d283b37fdb7fc1dcccbb88fc8f48a4aa4
treedecee9b3c3580fa20e8ef903870fc22bf14b457a
parente5f32ad56b22ebe384a6e7ddad6e9520c5495563
perf/x86/intel: Add a distinct name for Granite Rapids

Currently, the Sapphire Rapids and Granite Rapids share the same PMU
name, sapphire_rapids. Because from the kernel’s perspective, GNR is
similar to SPR. The only key difference is that they support different
extra MSRs. The code path and the PMU name are shared.

However, from end users' perspective, they are quite different. Besides
the extra MSRs, GNR has a newer PEBS format, supports Retire Latency,
supports new CPUID enumeration architecture, doesn't required the
load-latency AUX event, has additional TMA Level 1 Architectural Events,
etc. The differences can be enumerated by CPUID or the PERF_CAPABILITIES
MSR. They weren't reflected in the model-specific kernel setup.
But it is worth to have a distinct PMU name for GNR.

Fixes: a6742cb90b56 ("perf/x86/intel: Fix the FRONTEND encoding on GNR and MTL")
Suggested-by: Ahmad Yasin <ahmad.yasin@intel.com>
Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: stable@vger.kernel.org
Link: https://lkml.kernel.org/r/20240708193336.1192217-3-kan.liang@linux.intel.com
arch/x86/events/intel/core.c