From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, xiaoyao.li@intel.com
Subject: [PATCH 0/3] KVM: x86: BUS_LOCK_EXIT fixes
Date: Thu, 6 Aug 2026 19:19:20 +0800 [thread overview]
Message-ID: <20260806111923.1990562-1-xiaoyao.li@intel.com> (raw)
This series contains fixes for x86 Bus Lock Exit feature.
Patch 1 fixes a bug which is somewhat discovered by Sashiko, when it
reviewed the TDX Bus Lock Exit enabling patch [1]. It pointed out one
issue for the TDX patch, and I found the existing VMX code has the same
issue.
Patch 2 and patch 3 fix the issues for KVM_CAP_X86_BUS_LOCK_EXIT,
which were found When I tested the TDX Bus Lock Exit enabling patch.
[1] https://lore.kernel.org/all/20260805034602.5B2BB1F000E9@smtp.kernel.org/
Xiaoyao Li (3):
KVM: VMX: Preserve negative return value in vmx_handle_exit() with bus
lock detected
KVM: x86: Reject enabling KVM_CAP_X86_BUS_LOCK_EXIT when
!kvm_caps.has_bus_lock_exit
KVM: x86: Only allow enabling KVM_BUS_LOCK_DETECTION_EXIT before
creating any vCPU
arch/x86/kvm/vmx/vmx.c | 5 +++--
arch/x86/kvm/x86.c | 14 +++++++++++---
2 files changed, 14 insertions(+), 5 deletions(-)
base-commit: a806d364ef288a6443a1337820ea8410a7ccc6b3
--
2.43.0
next reply other threads:[~2026-08-06 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 11:19 Xiaoyao Li [this message]
2026-08-06 11:19 ` [PATCH 1/3] KVM: VMX: Preserve negative return value in vmx_handle_exit() with bus lock detected Xiaoyao Li
2026-08-06 11:19 ` [PATCH 2/3] KVM: x86: Reject enabling KVM_CAP_X86_BUS_LOCK_EXIT when !kvm_caps.has_bus_lock_exit Xiaoyao Li
2026-08-06 14:31 ` Sean Christopherson
2026-08-06 11:19 ` [PATCH 3/3] KVM: x86: Only allow enabling KVM_BUS_LOCK_DETECTION_EXIT before creating any vCPU Xiaoyao Li
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=20260806111923.1990562-1-xiaoyao.li@intel.com \
--to=xiaoyao.li@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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
all inboxes | Powered by JetHome®