From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: sashiko-reviews@lists.linux.dev,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH v3 3/4] KVM: TDX: Don't assume exit_reason[31:16] as all-0 in tdx_to_vmx_exit_reason()
Date: Thu, 13 Aug 2026 16:42:25 +0800 [thread overview]
Message-ID: <0e7524d5-8798-49fd-b8a8-9d7e5977f23c@intel.com> (raw)
In-Reply-To: <an0MdQKMHclUjW9r@google.com>
On 8/13/2026 8:14 AM, Sean Christopherson wrote:
> On Wed, Aug 12, 2026, Xiaoyao Li wrote:
>> On 8/12/2026 4:23 PM, sashiko-bot@kernel.org wrote:
>>>> diff --git a/arch/x86/kvm/vmx/tdx.c b/arch/x86/kvm/vmx/tdx.c
>>> When the basic exit reason is set to TDX_INVALID_EXIT_REASON here, but upper
>>> bits like Bus Lock are preserved in exit_reason.full, does this break
>>> tdx_get_exit_info()?
>>>
>>> In tdx_get_exit_info(), it evaluates against the full 32-bit exit reason:
>>>
>>> *reason = tdx->vt.exit_reason.full;
>>> if (*reason != TDX_INVALID_EXIT_REASON) {
>>> *info1 = vmx_get_exit_qual(vcpu);
>>> ...
>>>
>>> Since TDX_INVALID_EXIT_REASON is the 16-bit 0xFFFF, this check will pass if
>>> any upper bits are set, even if the basic reason was marked invalid,
>>> incorrectly exposing meaningless hardware state.
>>
>> Oh, I should have called it out it's intentional to check the full 32 bits
>> Exit Reason instead of checking the lower 16 bits .basic field as what it
>> did in the v2.
>
> Please wait for discussion to die down before sending new versions. You sent
> this version literally the same day you responded to some of my comments on v2.
> Now the discussion is spread across different mail threads and I'm having to
> piece the converation together.
>
> In short, spamming versions makes it harder to review, and thus slows the process
> down; it doesn't speed things up.
My apologies for this.
next prev parent reply other threads:[~2026-08-13 8:42 UTC|newest]
Thread overview: 17+ 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-13 8:42 ` Xiaoyao Li [this message]
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
2026-08-12 22:58 ` Edgecombe, Rick P
2026-08-13 11:17 ` Xiaoyao Li
2026-08-13 14:43 ` 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=0e7524d5-8798-49fd-b8a8-9d7e5977f23c@intel.com \
--to=xiaoyao.li@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--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 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.