From: Jim Mattson <jmattson@google.com>
To: seanjc@google.com, pbonzini@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
nikunj@amd.com, yosry@kernel.org,
Jim Mattson <jmattson@google.com>
Subject: [PATCH v2 4/4] KVM: selftests: Add coverage for the EFER_LMSLE_MBZ defeature
Date: Wed, 23 Sep 2026 17:25:45 -0700 [thread overview]
Message-ID: <f0ce99261caf71e88cd0d51a4053abb77454e8bf.1790208413.git.jmattson@google.com> (raw)
In-Reply-To: <cover.1790208413.git.jmattson@google.com>
Add coverage for KVM's virtualization of EFER_LMSLE_MBZ,
CPUID.80000008H:EBX[bit 20], which is set when the CPU does *not* support long
mode segment limits. Verify that KVM's enumeration of the defeature matches
the expectation derived from hardware plus kvm_amd's "nested" module param, so
that the assertion doesn't compare KVM's enumeration against itself, and that
WRMSR(EFER), nested VMRUN, and KVM_SET_SREGS reject EFER.LMSLE=1 if and only
if guest CPUID enumerates the defeature. Also verify that host-initiated
KVM_SET_MSRS is exempt from the check, as host-initiated writes skip guest
CPUID checks so that userspace can set MSRs before it sets guest CPUID.
Extend svm_nested_efer_test rather than add yet another test binary for a
single CPUID bit; the test already has the L1/L2 harness needed to exercise
EFER.LMSLE. Note, only a CPU that supports LMSLE, i.e. Rome and earlier,
exercises the emulation path; elsewhere KVM enumerates the defeature straight
from hardware.
Opportunistically drop the unnecessary #include of vmx.h.
Assisted-by: LLM
Signed-off-by: Jim Mattson <jmattson@google.com>
---
.../selftests/kvm/include/x86/processor.h | 1 +
.../selftests/kvm/x86/svm_nested_efer_test.c | 249 +++++++++++++++++-
2 files changed, 237 insertions(+), 13 deletions(-)
diff --git a/tools/testing/selftests/kvm/include/x86/processor.h b/tools/testing/selftests/kvm/include/x86/processor.h
index 6e6f70035508..ba5d8b37edc1 100644
--- a/tools/testing/selftests/kvm/include/x86/processor.h
+++ b/tools/testing/selftests/kvm/include/x86/processor.h
@@ -216,6 +216,7 @@ struct kvm_x86_cpu_feature {
#define X86_FEATURE_INVTSC KVM_X86_CPU_FEATURE(0x80000007, 0, EDX, 8)
#define X86_FEATURE_RDPRU KVM_X86_CPU_FEATURE(0x80000008, 0, EBX, 4)
#define X86_FEATURE_AMD_IBPB KVM_X86_CPU_FEATURE(0x80000008, 0, EBX, 12)
+#define X86_FEATURE_EFER_LMSLE_MBZ KVM_X86_CPU_FEATURE(0x80000008, 0, EBX, 20)
#define X86_FEATURE_NPT KVM_X86_CPU_FEATURE(0x8000000A, 0, EDX, 0)
#define X86_FEATURE_LBRV KVM_X86_CPU_FEATURE(0x8000000A, 0, EDX, 1)
#define X86_FEATURE_NRIPS KVM_X86_CPU_FEATURE(0x8000000A, 0, EDX, 3)
diff --git a/tools/testing/selftests/kvm/x86/svm_nested_efer_test.c b/tools/testing/selftests/kvm/x86/svm_nested_efer_test.c
index 6bc301207cbc..765476c79c96 100644
--- a/tools/testing/selftests/kvm/x86/svm_nested_efer_test.c
+++ b/tools/testing/selftests/kvm/x86/svm_nested_efer_test.c
@@ -1,16 +1,20 @@
// SPDX-License-Identifier: GPL-2.0-only
/*
+ * Tests for KVM's handling of EFER bits whose behavior is tied to nested SVM.
+ *
* Copyright (C) 2026, Google LLC.
*/
+#include "test_util.h"
#include "kvm_util.h"
-#include "vmx.h"
+#include "processor.h"
#include "svm_util.h"
#include "kselftest.h"
+static bool l2_ran;
-static void l2_guest_code(void)
+static void l2_clear_efer_svme(void)
{
- unsigned long efer = rdmsr(MSR_EFER);
+ u64 efer = rdmsr(MSR_EFER);
/* generic_svm_setup() initializes EFER_SVME set for L2 */
GUEST_ASSERT(efer & EFER_SVME);
@@ -20,31 +24,250 @@ static void l2_guest_code(void)
GUEST_ASSERT(0);
}
-static void l1_guest_code(struct svm_test_data *svm)
+static void l1_clear_efer_svme(struct svm_test_data *svm)
{
- generic_svm_setup(svm, l2_guest_code);
+ generic_svm_setup(svm, l2_clear_efer_svme);
run_guest(svm->vmcb, svm->vmcb_gpa);
/* Unreachable, L1 should be shutdown */
GUEST_ASSERT(0);
}
-int main(int argc, char *argv[])
+static void l2_lmsle(void)
+{
+ GUEST_ASSERT(rdmsr(MSR_EFER) & EFER_LMSLE);
+ l2_ran = true;
+ vmmcall();
+}
+
+static void l1_lmsle(struct svm_test_data *svm)
+{
+ bool lmsle_mbz = this_cpu_has(X86_FEATURE_EFER_LMSLE_MBZ);
+ struct vmcb *vmcb = svm->vmcb;
+ u64 efer = rdmsr(MSR_EFER);
+
+ /*
+ * Selftests' vCPUs are created with EFER.LMSLE clear; the sub-tests
+ * below need to start from a clean slate.
+ */
+ GUEST_ASSERT(!(efer & EFER_LMSLE));
+ GUEST_ASSERT(!l2_ran);
+
+ /*
+ * Per AMD APM vol. 2, if CPUID.80000008H:EBX[bit 20] is set, "64-bit
+ * mode segment limit checking is not supported and attempting to set
+ * EFER.LMSLE = 1 causes a #GP exception".
+ */
+ if (lmsle_mbz) {
+ GUEST_ASSERT_EQ(wrmsr_safe(MSR_EFER, efer | EFER_LMSLE), GP_VECTOR);
+ GUEST_ASSERT(!(rdmsr(MSR_EFER) & EFER_LMSLE));
+ } else {
+ GUEST_ASSERT_EQ(wrmsr_safe(MSR_EFER, efer | EFER_LMSLE), 0);
+ GUEST_ASSERT(rdmsr(MSR_EFER) & EFER_LMSLE);
+
+ /*
+ * Restore EFER so that generic_svm_setup() doesn't propagate
+ * EFER.LMSLE into vmcb12 on its own, i.e. so that the VMRUN
+ * sub-test actually tests what it thinks it's testing.
+ */
+ wrmsr(MSR_EFER, efer);
+ }
+
+ /*
+ * VMRUN's consistency checks reject "any MBZ bit of EFER", i.e. a
+ * vmcb12 with EFER.LMSLE set must generate VMEXIT_INVALID when the
+ * defeature is enumerated.
+ */
+ generic_svm_setup(svm, l2_lmsle);
+ vmcb->save.efer |= EFER_LMSLE;
+ run_guest(vmcb, svm->vmcb_gpa);
+
+ if (lmsle_mbz) {
+ GUEST_ASSERT_EQ(vmcb->control.exit_code, SVM_EXIT_ERR);
+ GUEST_ASSERT(!l2_ran);
+ } else {
+ GUEST_ASSERT_EQ(vmcb->control.exit_code, SVM_EXIT_VMMCALL);
+ GUEST_ASSERT(l2_ran);
+ GUEST_ASSERT(vmcb->save.efer & EFER_LMSLE);
+ }
+
+ GUEST_DONE();
+}
+
+static struct kvm_vcpu *create_l1_vcpu(struct kvm_vm **vm, void *l1_guest_code)
{
struct kvm_vcpu *vcpu;
- struct kvm_vm *vm;
- gva_t nested_gva = 0;
+ gva_t svm_gva;
- TEST_REQUIRE(kvm_cpu_has(X86_FEATURE_SVM));
+ *vm = vm_create_with_one_vcpu(&vcpu, l1_guest_code);
- vm = vm_create_with_one_vcpu(&vcpu, l1_guest_code);
+ vcpu_alloc_svm(*vm, &svm_gva);
+ vcpu_args_set(vcpu, 1, svm_gva);
+
+ return vcpu;
+}
+
+static void test_enumeration(void)
+{
+ bool lmsle_mbz;
- vcpu_alloc_svm(vm, &nested_gva);
- vcpu_args_set(vcpu, 1, nested_gva);
+ /*
+ * EFER_LMSLE_MBZ, CPUID.80000008H:EBX[bit 20], is a "defeature" bit,
+ * i.e. is set when the CPU does *not* support long mode segment
+ * limits. KVM enumerates the defeature if and only if KVM refuses to
+ * set EFER.LMSLE, i.e. if the CPU doesn't support LMSLE, or if KVM
+ * doesn't support nested SVM. Derive the expectation from raw CPUID
+ * and kvm_amd's "nested" module param rather than from
+ * kvm_cpu_has(X86_FEATURE_SVM), so that the assertion doesn't simply
+ * compare KVM's enumeration to itself.
+ *
+ * Note, kvm_amd's "nested" is an "int" module param, i.e. reads back
+ * as '1'/'0' and not as 'Y'/'N'. Query the param if and only if the
+ * CPU supports SVM, i.e. if and only if kvm_amd is the module in
+ * play. Checking the vendor string wouldn't suffice, e.g. Zhaoxin
+ * and Centaur CPUs are "GenuineIntel"-adjacent at best, but run VMX
+ * and thus load kvm_intel.
+ */
+ lmsle_mbz = this_cpu_has(X86_FEATURE_EFER_LMSLE_MBZ) ||
+ !this_cpu_has(X86_FEATURE_SVM) ||
+ !get_kvm_amd_param_integer("nested");
+
+ TEST_ASSERT_EQ(kvm_cpu_has(X86_FEATURE_EFER_LMSLE_MBZ), lmsle_mbz);
+
+ ksft_test_result_pass("KVM enumerates EFER_LMSLE_MBZ=%d\n", lmsle_mbz);
+}
+
+static void test_clear_efer_svme(void)
+{
+ struct kvm_vcpu *vcpu;
+ struct kvm_vm *vm;
+
+ vcpu = create_l1_vcpu(&vm, l1_clear_efer_svme);
vcpu_run(vcpu);
TEST_ASSERT_KVM_EXIT_REASON(vcpu, KVM_EXIT_SHUTDOWN);
kvm_vm_free(vm);
- return 0;
+ ksft_test_result_pass("L2 clearing EFER.SVME shuts down L1\n");
+}
+
+static void test_lmsle(bool lmsle_mbz)
+{
+ struct kvm_vcpu *vcpu;
+ struct kvm_vm *vm;
+ struct ucall uc;
+
+ vcpu = create_l1_vcpu(&vm, l1_lmsle);
+
+ vcpu_set_or_clear_cpuid_feature(vcpu, X86_FEATURE_EFER_LMSLE_MBZ,
+ lmsle_mbz);
+
+ vcpu_run(vcpu);
+ TEST_ASSERT_KVM_EXIT_REASON(vcpu, KVM_EXIT_IO);
+
+ switch (get_ucall(vcpu, &uc)) {
+ case UCALL_ABORT:
+ REPORT_GUEST_ASSERT(uc);
+ case UCALL_DONE:
+ break;
+ default:
+ TEST_FAIL("Unexpected ucall: %lu", uc.cmd);
+ }
+
+ kvm_vm_free(vm);
+ ksft_test_result_pass("Guest EFER_LMSLE_MBZ=%d\n", lmsle_mbz);
+}
+
+static void test_host_initiated_lmsle(void)
+{
+ struct kvm_vcpu *vcpu;
+ struct kvm_vm *vm;
+ u64 efer;
+
+ vm = vm_create_with_one_vcpu(&vcpu, NULL);
+ vcpu_set_cpuid_feature(vcpu, X86_FEATURE_EFER_LMSLE_MBZ);
+
+ /*
+ * EFER_LMSLE_MBZ is a guest CPUID consistency check, not a host
+ * capability, i.e. must not be enforced against host-initiated writes,
+ * so that userspace can set MSRs before it sets guest CPUID.
+ */
+ efer = vcpu_get_msr(vcpu, MSR_EFER);
+ TEST_ASSERT(!(efer & EFER_LMSLE), "EFER.LMSLE unexpectedly set");
+
+ vcpu_set_msr(vcpu, MSR_EFER, efer | EFER_LMSLE);
+ TEST_ASSERT_EQ(vcpu_get_msr(vcpu, MSR_EFER), efer | EFER_LMSLE);
+
+ kvm_vm_free(vm);
+ ksft_test_result_pass("Host-initiated EFER.LMSLE=1 is allowed\n");
+}
+
+static void test_sregs_lmsle(void)
+{
+ struct kvm_vcpu *vcpu;
+ struct kvm_sregs sregs;
+ struct kvm_vm *vm;
+ int rc;
+
+ vm = vm_create_with_one_vcpu(&vcpu, NULL);
+ vcpu_set_cpuid_feature(vcpu, X86_FEATURE_EFER_LMSLE_MBZ);
+
+ /*
+ * Unlike KVM_SET_MSRS, KVM_SET_SREGS runs the full set of guest CPUID
+ * checks, i.e. rejects EFER.LMSLE even though it's host-initiated.
+ */
+ vcpu_sregs_get(vcpu, &sregs);
+ TEST_ASSERT(!(sregs.efer & EFER_LMSLE), "EFER.LMSLE unexpectedly set");
+
+ sregs.efer |= EFER_LMSLE;
+ rc = _vcpu_sregs_set(vcpu, &sregs);
+ TEST_ASSERT(rc, "KVM allowed EFER.LMSLE with EFER_LMSLE_MBZ set");
+
+ kvm_vm_free(vm);
+ ksft_test_result_pass("KVM_SET_SREGS rejects EFER.LMSLE=1\n");
+}
+
+int main(int argc, char *argv[])
+{
+ bool has_nested_svm, has_lmsle;
+
+ ksft_print_header();
+ ksft_set_plan(6);
+
+ test_enumeration();
+
+ /*
+ * The sub-tests below need to actually run a nested guest, and the
+ * EFER.LMSLE sub-tests additionally need KVM to allow EFER.LMSLE.
+ * It's KVM's view of the world, not raw CPUID, that dictates whether
+ * EFER.LMSLE is allowed, i.e. whether the defeature is emulated.
+ */
+ has_nested_svm = kvm_cpu_has(X86_FEATURE_SVM);
+ has_lmsle = has_nested_svm &&
+ !kvm_cpu_has(X86_FEATURE_EFER_LMSLE_MBZ);
+
+ if (!has_nested_svm)
+ ksft_print_msg("Nested SVM unsupported\n");
+ else if (!has_lmsle)
+ ksft_print_msg("KVM doesn't support EFER.LMSLE\n");
+
+ if (has_nested_svm) {
+ test_clear_efer_svme();
+ test_lmsle(true);
+ } else {
+ ksft_test_result_skip("L2 clearing EFER.SVME shuts down L1\n");
+ ksft_test_result_skip("Guest EFER_LMSLE_MBZ=1\n");
+ }
+
+ if (has_lmsle) {
+ test_lmsle(false);
+ test_host_initiated_lmsle();
+ test_sregs_lmsle();
+ } else {
+ ksft_test_result_skip("Guest EFER_LMSLE_MBZ=0\n");
+ ksft_test_result_skip("Host-initiated EFER.LMSLE=1 is allowed\n");
+ ksft_test_result_skip("KVM_SET_SREGS rejects EFER.LMSLE=1\n");
+ }
+
+ ksft_finished();
}
--
2.56.0.rc1.315.gc6ed9934b7-goog
prev parent reply other threads:[~2026-09-24 0:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 0:25 [PATCH v2 0/4] KVM: x86: Honor EFER_LMSLE_MBZ Jim Mattson
2026-09-24 0:25 ` [PATCH v2 1/4] KVM: x86: Advertise EFER_LMSLE_MBZ when KVM disallows EFER.LMSLE Jim Mattson
2026-09-24 0:25 ` [PATCH v2 2/4] KVM: x86: Honor the guest's EFER_LMSLE_MBZ Jim Mattson
2026-09-24 0:25 ` [PATCH v2 3/4] KVM: selftests: Rename svm_nested_clear_efer_svme to svm_nested_efer_test Jim Mattson
2026-09-24 0:25 ` Jim Mattson [this message]
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=f0ce99261caf71e88cd0d51a4053abb77454e8bf.1790208413.git.jmattson@google.com \
--to=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=yosry@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
all inboxes | Powered by JetHome®