From: Jiaxi Chen <jiaxi.chen@linux.intel.com>
To: kvm@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
seanjc@google.com, pbonzini@redhat.com, ndesaulniers@google.com,
alexandre.belloni@bootlin.com, peterz@infradead.org,
jpoimboe@kernel.org, chang.seok.bae@intel.com,
pawan.kumar.gupta@linux.intel.com, babu.moger@amd.com,
jmattson@google.com, sandipan.das@amd.com, tony.luck@intel.com,
sathyanarayanan.kuppuswamy@linux.intel.com, fenghua.yu@intel.com,
keescook@chromium.org, nathan@kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/7] x86: KVM: Advertise CPUID of new Intel platform
Date: Thu, 10 Nov 2022 09:52:45 +0800 [thread overview]
Message-ID: <20221110015252.202566-1-jiaxi.chen@linux.intel.com> (raw)
Latest Intel platform Granite Rapids/Sierra Forest has introduced below
new instructions and CPUIDs:
- CMPccXADD CPUID.(EAX=7,ECX=1):EAX[bit 7]
- AMX-FP16 CPUID.(EAX=7,ECX=1):EAX[bit 21]
- AVX-IFMA CPUID.(EAX=7,ECX=1):EAX[bit 23]
- AVX-VNNI-INT8 CPUID.(EAX=7,ECX=1):EDX[bit 4]
- AVX-NE-CONVERT CPUID.(EAX=7,ECX=1):EDX[bit 5]
- PREFETCHITI CPUID.(EAX=7,ECX=1):EDX[bit 14]
Details can be found in recent Intel ISE (Instruction Set
Extensions)[1].
This patch series advertises KVM support of these CPUIDs to host
userspace.
[1] Intel ISE: https://cdrdv2.intel.com/v1/dl/getContent/671368
v3:
- Remain CPUID_8000_001F_EAX in the last leaf of cpuid_leaf[]
- Replace CPUID_7_1_EAX with CPUID_LNX_5, waiting for future new CPUIDs
v2:
https://lore.kernel.org/all/20221103025030.78371-1-jiaxi.chen@linux.intel.com/
- Remove vague descriptions in the changelogs, including pronouns and
"this patch" kind of things.
- Move the two CPUIDs of cpuid_leaf[12] CPUID_7_1_EAX to kvm-only
subleaves.
- Replace cpuid_leaf[12] CPUID_7_1_EAX with the last leaf
CPUID_8000_001F_EAX to shorten array length.
- Change the newly-added CPUID leaf [CPUID_7_1_EDX] in v1 into kvm-only
subleaves.
v1:
https://lore.kernel.org/all/20221019084734.3590760-1-jiaxi.chen@linux.intel.com/
Jiaxi Chen (7):
x86: KVM: Move existing x86 CPUID leaf [CPUID_7_1_EAX] to kvm-only
leaf
x86: KVM: Advertise CMPccXADD CPUID to user space
x86: KVM: Advertise AMX-FP16 CPUID to user space
x86: KVM: Advertise AVX-IFMA CPUID to user space
x86: KVM: Advertise AVX-VNNI-INT8 CPUID to user space
x86: KVM: Advertise AVX-NE-CONVERT CPUID to user space
x86: KVM: Advertise PREFETCHIT0/1 CPUID to user space
arch/x86/include/asm/cpufeature.h | 2 +-
arch/x86/include/asm/cpufeatures.h | 4 +---
arch/x86/kernel/cpu/common.c | 6 ------
arch/x86/kernel/cpu/cpuid-deps.c | 1 -
arch/x86/kvm/cpuid.c | 11 ++++++++---
arch/x86/kvm/reverse_cpuid.h | 15 +++++++++++++++
6 files changed, 25 insertions(+), 14 deletions(-)
base-commit: 30a0b95b1335e12efef89dd78518ed3e4a71a763
--
2.27.0
next reply other threads:[~2022-11-10 1:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 1:52 Jiaxi Chen [this message]
2022-11-10 1:52 ` [PATCH v3 1/7] x86: KVM: Move existing x86 CPUID leaf [CPUID_7_1_EAX] to kvm-only leaf Jiaxi Chen
2022-11-15 13:50 ` Xiaoyao Li
2022-11-15 15:29 ` Sean Christopherson
2022-11-15 16:16 ` Borislav Petkov
2022-11-16 2:27 ` Jiaxi Chen
2022-11-10 1:52 ` [PATCH v3 2/7] x86: KVM: Advertise CMPccXADD CPUID to user space Jiaxi Chen
2022-11-10 1:52 ` [PATCH v3 3/7] x86: KVM: Advertise AMX-FP16 " Jiaxi Chen
2022-11-10 1:52 ` [PATCH v3 4/7] x86: KVM: Advertise AVX-IFMA " Jiaxi Chen
2022-11-10 1:52 ` [PATCH v3 5/7] x86: KVM: Advertise AVX-VNNI-INT8 " Jiaxi Chen
2022-11-10 1:52 ` [PATCH v3 6/7] x86: KVM: Advertise AVX-NE-CONVERT " Jiaxi Chen
2022-11-10 1:52 ` [PATCH v3 7/7] x86: KVM: Advertise PREFETCHIT0/1 " Jiaxi 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=20221110015252.202566-1-jiaxi.chen@linux.intel.com \
--to=jiaxi.chen@linux.intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=jpoimboe@kernel.org \
--cc=keescook@chromium.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).