[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221228113454.1199118-1-rodrigo.vivi@intel.com>
Date: Wed, 28 Dec 2022 06:34:54 -0500
From: Rodrigo Vivi <rodrigo.vivi@...el.com>
To: <x86@...nel.org>, <linux-perf-users@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
CC: Zhang Rui <rui.zhang@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Chris Wilson <chris@...is-wilson.co.uk>,
Rodrigo Vivi <rodrigo.vivi@...el.com>
Subject: [PATCH] x86/rapl: Treat Tigerlake like Icelake
From: Chris Wilson <chris@...is-wilson.co.uk>
Since Tigerlake seems to have inherited its cstates and other rapl power
caps from Icelake, assume it also follows Icelake for its rapl events.
Signed-off-by: Chris Wilson <chris@...is-wilson.co.uk>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@...el.com>
---
Based on the recent additions it looks like Tigerlake was a missed
case in these events/rapl.c and that this old patch from Chris is the
right way to go.
I found this patch on our drm-intel's topic/core-for-CI branch while
rebasing it towards v6.2-rc1.
arch/x86/events/rapl.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/events/rapl.c b/arch/x86/events/rapl.c
index a829492bca4c..ae5779ea4417 100644
--- a/arch/x86/events/rapl.c
+++ b/arch/x86/events/rapl.c
@@ -800,6 +800,8 @@ static const struct x86_cpu_id rapl_model_match[] __initconst = {
X86_MATCH_INTEL_FAM6_MODEL(ICELAKE_X, &model_hsx),
X86_MATCH_INTEL_FAM6_MODEL(COMETLAKE_L, &model_skl),
X86_MATCH_INTEL_FAM6_MODEL(COMETLAKE, &model_skl),
+ X86_MATCH_INTEL_FAM6_MODEL(TIGERLAKE_L, &model_skl),
+ X86_MATCH_INTEL_FAM6_MODEL(TIGERLAKE, &model_skl),
X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE, &model_skl),
X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_L, &model_skl),
X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_N, &model_skl),
--
2.38.1
Powered by blists - more mailing lists