From: "tip-bot2 for Kan Liang" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Kan Liang <kan.liang@linux.intel.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: perf/core] perf/x86/cstate: Add new Raptor Lake S support
Date: Fri, 30 Sep 2022 09:31:13 -0000 [thread overview]
Message-ID: <166453027328.401.8394558986563267964.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20220928153331.3757388-3-kan.liang@linux.intel.com>
The following commit has been merged into the perf/core branch of tip:
Commit-ID: d12940d2ead51c6978e7d38b2abf12b833270b2a
Gitweb: https://git.kernel.org/tip/d12940d2ead51c6978e7d38b2abf12b833270b2a
Author: Kan Liang <kan.liang@linux.intel.com>
AuthorDate: Wed, 28 Sep 2022 08:33:30 -07:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Thu, 29 Sep 2022 12:20:53 +02:00
perf/x86/cstate: Add new Raptor Lake S support
>From the perspective of Intel cstate residency counters, the new
Raptor Lake S is the same as the other hybrid {ALDER,RAPTOP}LAKE.
Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lore.kernel.org/r/20220928153331.3757388-3-kan.liang@linux.intel.com
---
arch/x86/events/intel/cstate.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/events/intel/cstate.c b/arch/x86/events/intel/cstate.c
index 8ec23f4..a2834bc 100644
--- a/arch/x86/events/intel/cstate.c
+++ b/arch/x86/events/intel/cstate.c
@@ -685,6 +685,7 @@ static const struct x86_cpu_id intel_cstates_match[] __initconst = {
X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_N, &adl_cstates),
X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE, &adl_cstates),
X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_P, &adl_cstates),
+ X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_S, &adl_cstates),
{ },
};
MODULE_DEVICE_TABLE(x86cpu, intel_cstates_match);
next prev parent reply other threads:[~2022-09-30 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 15:33 [PATCH V2 1/4] perf/x86: " kan.liang
2022-09-28 15:33 ` [PATCH V2 2/4] perf/x86/msr: " kan.liang
2022-09-30 9:31 ` [tip: perf/core] " tip-bot2 for Kan Liang
2022-09-28 15:33 ` [PATCH V2 3/4] perf/x86/cstate: " kan.liang
2022-09-30 9:31 ` tip-bot2 for Kan Liang [this message]
2022-09-28 15:33 ` [PATCH V2 4/4] perf/x86/uncore: " kan.liang
2022-09-30 9:31 ` [tip: perf/core] " tip-bot2 for Kan Liang
2022-09-30 9:31 ` [tip: perf/core] perf/x86: " tip-bot2 for Kan Liang
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=166453027328.401.8394558986563267964.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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®