From: "tip-bot2 for Zide Chen" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Zide Chen <zide.chen@intel.com>, Ingo Molnar <mingo@kernel.org>,
Dapeng Mi <dapeng1.mi@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: perf/core] perf/x86/intel/cstate: Add Diamond Rapids support
Date: Tue, 16 Dec 2025 13:48:38 -0000 [thread overview]
Message-ID: <176589291813.510.6479806528717518018.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20251215182520.115822-3-zide.chen@intel.com>
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 7ac422cf7b16ec524bcd8e017459e328a4103f63
Gitweb: https://git.kernel.org/tip/7ac422cf7b16ec524bcd8e017459e328a4103f63
Author: Zide Chen <zide.chen@intel.com>
AuthorDate: Mon, 15 Dec 2025 10:25:20 -08:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Tue, 16 Dec 2025 14:35:59 +01:00
perf/x86/intel/cstate: Add Diamond Rapids support
>From a C-state residency profiling perspective, Diamond Rapids is
similar to SRF and GNR, supporting core C1/C6, module C6, and
package C2/C6 residency counters. Similar to CWF, the C1E residency
can be accessed via PMT only.
Signed-off-by: Zide Chen <zide.chen@intel.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Reviewed-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
Link: https://patch.msgid.link/20251215182520.115822-3-zide.chen@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 008f8ea..1e2658b 100644
--- a/arch/x86/events/intel/cstate.c
+++ b/arch/x86/events/intel/cstate.c
@@ -652,6 +652,7 @@ static const struct x86_cpu_id intel_cstates_match[] __initconst = {
X86_MATCH_VFM(INTEL_EMERALDRAPIDS_X, &icx_cstates),
X86_MATCH_VFM(INTEL_GRANITERAPIDS_X, &icx_cstates),
X86_MATCH_VFM(INTEL_GRANITERAPIDS_D, &icx_cstates),
+ X86_MATCH_VFM(INTEL_DIAMONDRAPIDS_X, &srf_cstates),
X86_MATCH_VFM(INTEL_TIGERLAKE_L, &icl_cstates),
X86_MATCH_VFM(INTEL_TIGERLAKE, &icl_cstates),
next prev parent reply other threads:[~2025-12-16 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 18:25 [PATCH 1/3] perf/x86/intel/cstate: Add Wildcat Lake support Zide Chen
2025-12-15 18:25 ` [PATCH 2/3] perf/x86/intel/cstate: Add Nova " Zide Chen
2025-12-16 13:48 ` [tip: perf/core] " tip-bot2 for Zide Chen
2025-12-15 18:25 ` [PATCH 3/3] perf/x86/intel/cstate: Add Diamond Rapids support Zide Chen
2025-12-16 13:48 ` tip-bot2 for Zide Chen [this message]
2025-12-16 1:51 ` [PATCH 1/3] perf/x86/intel/cstate: Add Wildcat Lake support Mi, Dapeng
2025-12-16 13:48 ` [tip: perf/core] " tip-bot2 for Zide Chen
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=176589291813.510.6479806528717518018.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=mingo@kernel.org \
--cc=x86@kernel.org \
--cc=zide.chen@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
all inboxes | Powered by JetHome®