All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Jim Mattson <jmattson@google.com>
Subject: [PATCH v3 0/5] KVM: x86: Honor EFER_LMSLE_MBZ
Date: Tue, 29 Sep 2026 17:21:35 -0700	[thread overview]
Message-ID: <20260930002140.3174449-1-seanjc@google.com> (raw)

Jim's series to try to clean up the EFER.LMSLE_MBZ mess (and what a mess it is).
I didn't touch the KVM patches, and barely touched the selftests, i.e. Jim's
testing from v2 should still hold.

v3: Slot in a patch to add kvm_is_nested_virtualization_enabled() instead of
    open coding the check and relying on the X86_FEATURE_SVM cheak to make
    sure it's kvm_amd.ko under the hood (the patch is constructed so that it
    will trigger a noisy conflict with the in-flight 
    host_cpu_is_intel_compatible).

v2: https://lore.kernel.org/all/cover.1790208413.git.jmattson@google.com

v1: https://lore.kernel.org/all/20260918154530.4129698-1-jmattson@google.com


Jim Mattson (4):
  KVM: x86: Advertise EFER_LMSLE_MBZ when KVM disallows EFER.LMSLE
  KVM: x86: Honor the guest's EFER_LMSLE_MBZ
  KVM: selftests: Rename svm_nested_clear_efer_svme to
    svm_nested_efer_test
  KVM: selftests: Add coverage for the EFER_LMSLE_MBZ defeature

Sean Christopherson (1):
  KVM: selftests: Add module param API to check if nested virtualization
    is enabled

 Documentation/virt/kvm/api.rst                |  25 ++
 arch/x86/kvm/cpuid.c                          |  20 ++
 arch/x86/kvm/msrs.c                           |  12 +-
 arch/x86/kvm/svm/svm.c                        |  21 +-
 arch/x86/kvm/vmx/vmx.c                        |   7 +
 arch/x86/kvm/x86.c                            |   9 +-
 tools/testing/selftests/kvm/Makefile.kvm      |   2 +-
 .../selftests/kvm/include/x86/processor.h     |  32 ++-
 .../kvm/x86/svm_nested_clear_efer_svme.c      |  50 ----
 .../selftests/kvm/x86/svm_nested_efer_test.c  | 266 ++++++++++++++++++
 10 files changed, 386 insertions(+), 58 deletions(-)
 delete mode 100644 tools/testing/selftests/kvm/x86/svm_nested_clear_efer_svme.c
 create mode 100644 tools/testing/selftests/kvm/x86/svm_nested_efer_test.c


base-commit: d4b7fb647204f0c81dfeae2d1a708e4d858e0c94
-- 
2.56.0.rc1.315.gc6ed9934b7-goog


             reply	other threads:[~2026-09-30  0:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  0:21 Sean Christopherson [this message]
2026-09-30  0:21 ` [PATCH v3 1/5] KVM: x86: Advertise EFER_LMSLE_MBZ when KVM disallows EFER.LMSLE Sean Christopherson
2026-09-30  0:21 ` [PATCH v3 2/5] KVM: x86: Honor the guest's EFER_LMSLE_MBZ Sean Christopherson
2026-09-30  0:21 ` [PATCH v3 3/5] KVM: selftests: Rename svm_nested_clear_efer_svme to svm_nested_efer_test Sean Christopherson
2026-09-30  0:21 ` [PATCH v3 4/5] KVM: selftests: Add module param API to check if nested virtualization is enabled Sean Christopherson
2026-09-30  0:31   ` sashiko-bot
2026-09-30  1:09     ` Sean Christopherson
2026-09-30  0:21 ` [PATCH v3 5/5] KVM: selftests: Add coverage for the EFER_LMSLE_MBZ defeature Sean Christopherson

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=20260930002140.3174449-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.