From: kan.liang@linux.intel.com
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
linux-kernel@vger.kernel.org
Cc: ak@linux.intel.com, eranian@google.com, irogers@google.com,
Kan Liang <kan.liang@linux.intel.com>
Subject: [PATCH 4/9] x86/cpufeatures: Add Architectural PerfMon Extension bit
Date: Thu, 1 Dec 2022 11:56:59 -0800 [thread overview]
Message-ID: <20221201195704.2330866-4-kan.liang@linux.intel.com> (raw)
In-Reply-To: <20221201195704.2330866-1-kan.liang@linux.intel.com>
From: Kan Liang <kan.liang@linux.intel.com>
CPUID.(EAX=07H, ECX=1):EAX[8] indicates whether the Architectural
PerfMon Extension leaf (CPUID leaf 23) is supported.
The "X86_FEATURE_..., word 12" is already mirrored from CPUID
"0x00000007:1 (EAX)". Add X86_FEATURE_ARCH_PERFMON_EXT under the
"word 12" section.
The new Architectural PerfMon Extension leaf (CPUID leaf 23) will be
supported in the perf_events subsystem later.
The feature will not appear in /proc/cpuinfo.
Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
---
arch/x86/include/asm/cpufeatures.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/include/asm/cpufeatures.h b/arch/x86/include/asm/cpufeatures.h
index b71f4f2ecdd5..9f05a0bb93ca 100644
--- a/arch/x86/include/asm/cpufeatures.h
+++ b/arch/x86/include/asm/cpufeatures.h
@@ -308,6 +308,7 @@
/* Intel-defined CPU features, CPUID level 0x00000007:1 (EAX), word 12 */
#define X86_FEATURE_AVX_VNNI (12*32+ 4) /* AVX VNNI instructions */
#define X86_FEATURE_AVX512_BF16 (12*32+ 5) /* AVX512 BFLOAT16 instructions */
+#define X86_FEATURE_ARCH_PERFMON_EXT (12*32+ 8) /* "" Intel Architectural PerfMon Extension */
/* AMD-defined CPU features, CPUID level 0x80000008 (EBX), word 13 */
#define X86_FEATURE_CLZERO (13*32+ 0) /* CLZERO instruction */
--
2.35.1
next prev parent reply other threads:[~2022-12-01 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 19:56 [PATCH 1/9] perf: Add PMU_FORMAT_ATTR_SHOW kan.liang
2022-12-01 19:56 ` [PATCH 2/9] perf/x86: Add Meteor Lake support kan.liang
2022-12-01 19:56 ` [PATCH 3/9] perf/x86: Support Retire Latency kan.liang
2022-12-01 19:56 ` kan.liang [this message]
2022-12-01 19:57 ` [PATCH 5/9] perf/x86/intel: Support Architectural PerfMon Extension leaf kan.liang
2022-12-01 19:57 ` [PATCH 6/9] perf/x86/cstate: Add Meteor Lake support kan.liang
2022-12-01 19:57 ` [PATCH 7/9] perf/x86/msr: " kan.liang
2022-12-01 19:57 ` [PATCH 8/9] perf report: Support Retire Latency kan.liang
2022-12-01 19:57 ` [PATCH 9/9] perf script: " 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=20221201195704.2330866-4-kan.liang@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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®