From: Sean Christopherson <seanjc@google.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: sashiko-reviews@lists.linux.dev, kvm@vger.kernel.org
Subject: Re: [PATCH v3 4/4] KVM: TDX: Enable Bus Lock VM exit
Date: Wed, 12 Aug 2026 17:06:58 -0700 [thread overview]
Message-ID: <an0KokdtSXE2GmM1@google.com> (raw)
In-Reply-To: <b66874a9-3f3f-4b65-90b1-b08c4aab6649@intel.com>
On Wed, Aug 12, 2026, Xiaoyao Li wrote:
> On 8/12/2026 4:20 PM, sashiko-bot@kernel.org wrote:
> > Pre-existing issues:
> > - [High] The preexisting VMX handler vmx_handle_exit() silently drops negative error codes when a bus lock is detected.
>
> As replied in the v2: VMX fix was sent already
>
> https://lore.kernel.org/all/20260806111923.1990562-2-xiaoyao.li@intel.com/
>
> BTW, Sean,
>
> Will you pick the VMX fix separately from the series, if it looks OK to you?
> So the next version of that series can focus on the general x86 CAP changes.
Given how close we are to the merge window, it probably makes sense to include
it in this series. It's not urgent enough to squeeze into 7.3-rc1, let alone 7.2,
so the very earliest I would grab it is 2.5 weeks from now.
next prev parent reply other threads:[~2026-08-13 0:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 8:02 [PATCH v3 0/4] KVM: TDX: Enable VM-DoS Prevention Features for TDX Xiaoyao Li
2026-08-12 8:02 ` [PATCH v3 1/4] KVM: TDX: Enable Notify VM exit Xiaoyao Li
2026-08-12 8:02 ` [PATCH v3 2/4] KVM: TDX: Set bits 31:16 to 0 for the synthesized Exit Reason Xiaoyao Li
2026-08-12 21:58 ` Edgecombe, Rick P
2026-08-12 8:02 ` [PATCH v3 3/4] KVM: TDX: Don't assume exit_reason[31:16] as all-0 in tdx_to_vmx_exit_reason() Xiaoyao Li
2026-08-12 8:23 ` sashiko-bot
2026-08-12 9:07 ` Xiaoyao Li
2026-08-12 22:55 ` Edgecombe, Rick P
2026-08-13 0:14 ` Sean Christopherson
2026-08-12 8:02 ` [PATCH v3 4/4] KVM: TDX: Enable Bus Lock VM exit Xiaoyao Li
2026-08-12 8:20 ` sashiko-bot
2026-08-12 9:11 ` Xiaoyao Li
2026-08-13 0:06 ` Sean Christopherson [this message]
2026-08-12 22:58 ` Edgecombe, Rick P
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=an0KokdtSXE2GmM1@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=xiaoyao.li@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