From: "tip-bot2 for Martin Schiller" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Martin Schiller <ms@dev.tdt.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Dapeng Mi <dapeng1.mi@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: perf/core] perf/x86/cstate: Add Airmont NP
Date: Wed, 17 Dec 2025 12:37:59 -0000 [thread overview]
Message-ID: <176597507931.510.4588704165245096188.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20251124074846.9653-4-ms@dev.tdt.de>
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 3006911f284d769b0f66c12b39da130325ef1440
Gitweb: https://git.kernel.org/tip/3006911f284d769b0f66c12b39da130325ef1440
Author: Martin Schiller <ms@dev.tdt.de>
AuthorDate: Mon, 24 Nov 2025 08:48:46 +01:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Wed, 17 Dec 2025 13:31:09 +01:00
perf/x86/cstate: Add Airmont NP
>From the perspective of Intel cstate residency counters, the Airmont NP
(aka Lightning Mountain) is identical to the Airmont.
Signed-off-by: Martin Schiller <ms@dev.tdt.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
Link: https://patch.msgid.link/20251124074846.9653-4-ms@dev.tdt.de
---
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 1e2658b..f3d5ee0 100644
--- a/arch/x86/events/intel/cstate.c
+++ b/arch/x86/events/intel/cstate.c
@@ -613,6 +613,7 @@ static const struct x86_cpu_id intel_cstates_match[] __initconst = {
X86_MATCH_VFM(INTEL_ATOM_SILVERMONT, &slm_cstates),
X86_MATCH_VFM(INTEL_ATOM_SILVERMONT_D, &slm_cstates),
X86_MATCH_VFM(INTEL_ATOM_AIRMONT, &slm_cstates),
+ X86_MATCH_VFM(INTEL_ATOM_AIRMONT_NP, &slm_cstates),
X86_MATCH_VFM(INTEL_BROADWELL, &snb_cstates),
X86_MATCH_VFM(INTEL_BROADWELL_D, &snb_cstates),
next prev parent reply other threads:[~2025-12-17 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 7:48 [PATCH 0/3] perf/x86: " Martin Schiller
2025-11-24 7:48 ` [PATCH 1/3] perf/x86/msr: " Martin Schiller
2025-12-17 12:38 ` [tip: perf/core] " tip-bot2 for Martin Schiller
2025-11-24 7:48 ` [PATCH 2/3] perf/x86/intel: " Martin Schiller
2025-12-17 12:38 ` [tip: perf/core] " tip-bot2 for Martin Schiller
2025-11-24 7:48 ` [PATCH 3/3] perf/x86/cstate: " Martin Schiller
2025-12-17 12:37 ` tip-bot2 for Martin Schiller [this message]
2025-11-25 7:44 ` [PATCH 0/3] perf/x86: " Mi, Dapeng
2025-12-17 7:33 ` Martin Schiller
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=176597507931.510.4588704165245096188.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=dapeng1.mi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=ms@dev.tdt.de \
--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®