From: Jim Mattson <jmattson@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Shuah Khan <shuah@kernel.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Clayton Pence <ctpence@google.com>
Cc: Jim Mattson <jmattson@google.com>
Subject: [PATCH 0/3] KVM: x86: Virtualize AMD CPUID faulting
Date: Thu, 2 Apr 2026 15:30:59 -0700 [thread overview]
Message-ID: <20260402223108.650572-1-jmattson@google.com> (raw)
AMD's "disable CPUID in usermode" feature is analogous to Intel's "CPUID
faulting" feature, but it is advertised and activated differently. The AMD
feature is advertised via CPUID.80000021H:EAX.CpuidUserDis[bit 17] and
activated by setting HWCR.CpuidUserDis[bit 35].
Add virtualization support for the AMD feature.
Jim Mattson (3):
KVM: x86: Rename supports_cpuid_fault to supports_intel_cpuid_fault
KVM: x86: Virtualize AMD CPUID faulting
KVM: selftests: Update hwcr_msr_test for CPUID faulting bit
arch/x86/kvm/cpuid.c | 2 +-
arch/x86/kvm/cpuid.h | 8 ++++---
arch/x86/kvm/emulate.c | 14 +++++++------
arch/x86/kvm/x86.c | 21 ++++++++++++-------
.../testing/selftests/kvm/x86/hwcr_msr_test.c | 2 +-
5 files changed, 29 insertions(+), 18 deletions(-)
base-commit: 3d6cdcc8883b5726513d245eef0e91cabfc397f7
--
2.53.0.1213.gd9a14994de-goog
next reply other threads:[~2026-04-02 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 22:30 Jim Mattson [this message]
2026-04-02 22:31 ` [PATCH 1/3] KVM: x86: Rename supports_cpuid_fault to supports_intel_cpuid_fault Jim Mattson
2026-04-10 22:21 ` Sean Christopherson
2026-04-10 22:22 ` Jim Mattson
2026-04-02 22:31 ` [PATCH 2/3] KVM: x86: Virtualize AMD CPUID faulting Jim Mattson
2026-04-02 22:31 ` [PATCH 3/3] KVM: selftests: Update hwcr_msr_test for CPUID faulting bit Jim Mattson
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=20260402223108.650572-1-jmattson@google.com \
--to=jmattson@google.com \
--cc=bp@alien8.de \
--cc=ctpence@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=tglx@kernel.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