From: Tao Su <tao1.su@linux.intel.com>
To: kvm@vger.kernel.org, x86@kernel.org
Cc: seanjc@google.com, pbonzini@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, chao.gao@intel.com,
xiaoyao.li@intel.com, jiaan.lu@intel.com, xuelian.guo@intel.com,
tao1.su@linux.intel.com
Subject: [PATCH 0/4] Advertise CPUID for new instructions in Clearwater Forest
Date: Mon, 4 Nov 2024 14:35:55 +0800 [thread overview]
Message-ID: <20241104063559.727228-1-tao1.su@linux.intel.com> (raw)
Latest Intel platform Clearwater Forest has introduced new instructions
for SHA512, SM3, SM4 and AVX-VNNI-INT16.
This patch set is for advertising these CPUIDs to userspace so that guests
can query them directly. Since these new instructions can't be intercepted
and only use xmm, ymm registers, host doesn't require to do additional
enabling for guest.
These new instructions are already updated into SDM [1].
---
[1] https://cdrdv2.intel.com/v1/dl/getContent/671200
Tao Su (4):
x86: KVM: Advertise SHA512 CPUID to userspace
x86: KVM: Advertise SM3 CPUID to userspace
x86: KVM: Advertise SM4 CPUID to userspace
KVM: x86: Advertise AVX-VNNI-INT16 CPUID to userspace
arch/x86/include/asm/cpufeatures.h | 3 +++
arch/x86/kvm/cpuid.c | 8 ++++----
arch/x86/kvm/reverse_cpuid.h | 1 +
3 files changed, 8 insertions(+), 4 deletions(-)
base-commit: 59b723cd2adbac2a34fc8e12c74ae26ae45bf230
--
2.34.1
next reply other threads:[~2024-11-04 6:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 6:35 Tao Su [this message]
2024-11-04 6:35 ` [PATCH 1/4] x86: KVM: Advertise SHA512 CPUID to userspace Tao Su
2024-11-04 6:35 ` [PATCH 2/4] x86: KVM: Advertise SM3 " Tao Su
2024-11-04 16:40 ` Dave Hansen
2024-11-05 0:58 ` Tao Su
2024-11-04 6:35 ` [PATCH 3/4] x86: KVM: Advertise SM4 " Tao Su
2024-11-04 6:35 ` [PATCH 4/4] KVM: x86: Advertise AVX-VNNI-INT16 " Tao Su
2024-11-04 6:51 ` [PATCH 0/4] Advertise CPUID for new instructions in Clearwater Forest Borislav Petkov
2024-11-04 7:04 ` Tao Su
2024-11-04 9:58 ` Borislav Petkov
2024-11-04 13:21 ` Tao Su
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=20241104063559.727228-1-tao1.su@linux.intel.com \
--to=tao1.su@linux.intel.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=jiaan.lu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=xuelian.guo@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