From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Kiryl Shutsemau <kas@kernel.org>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-coco@lists.linux.dev, nik.borisov@suse.com
Subject: Re: [PATCH v4 0/9] KVM: TDX: Enable VM-DoS Prevention Features for TDX
Date: Tue, 22 Sep 2026 10:02:28 +0800 [thread overview]
Message-ID: <d5a4ba72-3cce-4f16-ad47-f1c82c85d834@intel.com> (raw)
In-Reply-To: <arHDAVhFXeQXXrfI@google.com>
On 9/22/2026 7:51 AM, Sean Christopherson wrote:
> On Mon, Sep 21, 2026, Xiaoyao Li wrote:
>> On 8/19/2026 5:48 PM, Xiaoyao Li wrote:
>>> Hi all,
>>>
>>> This is v4 of the series to enable the Notify VM Exit and Bus Lock VM
>>> exit for TDX, which fixes the KVM CAP issue related with them and allow
>>> userspace to actually enable the features.
>>>
>>> Compared to v3, this v4 adds 5 more patches. The first 8 patches target
>>> for stable kernels while only the patch 9 doesn't have to. Patch 1 is a
>>> single patch to enable Notify VM exit for TDX. Except patch 6, patch
>>> 2-7 are mandatory for enabling Bus Lock VM exit for TDX in patch 8.
>>>
>>> Patch 6 itself is a fix for VMX and is OK for cc stable though maybe not
>>> necessary. Patch 6 is added to this series since it can help stop Sashiko
>>> repeating its finding of VMX's pre-existing issue, and it's also necessary
>>> for patch 9 to consilidate the exit handler for VMX and TDX.
>>>
>>> There are other issues of existing code found during previous review, like
>>> the EPT MISCONFIG handling. Given they are not mandatory for enabling the
>>> Notify VM exit and Bus Lock VM exit for TDX, the plan is to address them in
>>> a follow-up series separately.
>>>
>>> Please refer to v1 for a full background.
>>>
>>> v3: https://lore.kernel.org/all/20260812080229.2481439-1-xiaoyao.li@intel.com/
>>> v2: https://lore.kernel.org/all/20260810112200.2326727-1-xiaoyao.li@intel.com/
>>> v1: https://lore.kernel.org/all/20260805031257.1844914-1-xiaoyao.li@intel.com/
>>
>> Hi Sean,
>>
>> What's your plan on this series? Can you queue it if it looks good to you? Or
>> need me to spin a new version to address Binbin and Rick's comments on the
>> commit message?
>
> Get it applied, with some tweaks. I.e. no v5 necessary.
Thanks!
prev parent reply other threads:[~2026-09-22 2:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 9:48 Xiaoyao Li
2026-08-19 9:48 ` [PATCH v4 1/9] KVM: TDX: Enable Notify VM exit Xiaoyao Li
2026-08-20 8:48 ` Binbin Wu
2026-08-19 9:48 ` [PATCH v4 2/9] KVM: TDX: Check if there is valid exit infos based on vp_enter_ret Xiaoyao Li
2026-08-19 16:39 ` Edgecombe, Rick P
2026-08-20 1:53 ` Xiaoyao Li
2026-08-20 9:11 ` Binbin Wu
2026-08-19 9:48 ` [PATCH v4 3/9] KVM: TDX: Set bits 31:16 to 0 for the synthesized Exit Reason Xiaoyao Li
2026-08-20 9:16 ` Binbin Wu
2026-09-21 23:54 ` Sean Christopherson
2026-08-19 9:48 ` [PATCH v4 4/9] KVM: TDX: Don't assume exit_reason[31:16] is all-0 in tdx_to_vmx_exit_reason() Xiaoyao Li
2026-08-19 9:48 ` [PATCH v4 5/9] KVM: TDX: Update exit_reason on wait_for_sept_zap return Xiaoyao Li
2026-08-19 19:08 ` Edgecombe, Rick P
2026-08-19 9:49 ` [PATCH v4 6/9] KVM: VMX: Preserve negative return value in vmx_handle_exit() with bus lock detected Xiaoyao Li
2026-08-19 9:49 ` [PATCH v4 7/9] KVM: VMX: Make handle_bus_lock_vmexit() a shared helper Xiaoyao Li
2026-08-26 10:38 ` Nikolay Borisov
2026-08-19 9:49 ` [PATCH v4 8/9] KVM: TDX: Enable Bus Lock VM exit Xiaoyao Li
2026-08-26 10:38 ` Nikolay Borisov
2026-08-19 9:49 ` [PATCH v4 9/9] KVM: VMX: Consolidate the exit handler for VMX and TDX Xiaoyao Li
2026-08-26 9:51 ` Nikolay Borisov
2026-08-26 10:03 ` Nikolay Borisov
2026-08-26 10:43 ` Xiaoyao Li
2026-08-26 11:03 ` Nikolay Borisov
2026-08-26 13:59 ` Sean Christopherson
2026-08-19 22:57 ` [PATCH v4 0/9] KVM: TDX: Enable VM-DoS Prevention Features for TDX Edgecombe, Rick P
2026-08-19 23:03 ` Sean Christopherson
2026-08-19 23:08 ` Edgecombe, Rick P
2026-08-21 13:14 ` Sean Christopherson
2026-09-19 0:27 ` Vishal Annapurve
2026-09-21 14:44 ` Xiaoyao Li
2026-09-21 23:51 ` Sean Christopherson
2026-09-22 2:02 ` Xiaoyao Li [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=d5a4ba72-3cce-4f16-ad47-f1c82c85d834@intel.com \
--to=xiaoyao.li@intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.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®