From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "Li, Xiaoyao" <xiaoyao.li@intel.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"seanjc@google.com" <seanjc@google.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"kas@kernel.org" <kas@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nik.borisov@suse.com" <nik.borisov@suse.com>
Subject: Re: [PATCH v4 0/9] KVM: TDX: Enable VM-DoS Prevention Features for TDX
Date: Wed, 19 Aug 2026 22:57:48 +0000 [thread overview]
Message-ID: <5799b5d637f6b540c45874120aa37749a7dfb955.camel@intel.com> (raw)
In-Reply-To: <20260819094903.3060020-1-xiaoyao.li@intel.com>
On Wed, 2026-08-19 at 17:48 +0800, Xiaoyao Li wrote:
> 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.
To me this is not a valid reason. Sashiko is great, but we can't let false
positives drive the patches. Given that the series is so big now, I'd think it
would be better to leave 6 and 9 for follow up, so we can focus on the core
thing.
next prev parent reply other threads:[~2026-08-19 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 9:48 [PATCH v4 0/9] KVM: TDX: Enable VM-DoS Prevention Features for TDX Xiaoyao Li
2026-08-19 9:48 ` [PATCH v4 1/9] KVM: TDX: Enable Notify VM exit Xiaoyao Li
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-19 9:48 ` [PATCH v4 3/9] KVM: TDX: Set bits 31:16 to 0 for the synthesized Exit Reason Xiaoyao Li
[not found] ` <20260819094903.3060020-6-xiaoyao.li@intel.com>
2026-08-19 19:08 ` [PATCH v4 5/9] KVM: TDX: Update exit_reason on wait_for_sept_zap return Edgecombe, Rick P
2026-08-19 22:57 ` Edgecombe, Rick P [this message]
2026-08-19 23:03 ` [PATCH v4 0/9] KVM: TDX: Enable VM-DoS Prevention Features for TDX Sean Christopherson
2026-08-19 23:08 ` 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=5799b5d637f6b540c45874120aa37749a7dfb955.camel@intel.com \
--to=rick.p.edgecombe@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=seanjc@google.com \
--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