From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "Li, Xiaoyao" <xiaoyao.li@intel.com>,
"seanjc@google.com" <seanjc@google.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"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 v2 2/3] KVM: TDX: Fix the exit reason handling
Date: Thu, 13 Aug 2026 18:19:01 +0000 [thread overview]
Message-ID: <c2093dc50d2603c90fd40c7544561eb95d017898.camel@intel.com> (raw)
In-Reply-To: <an0M-LwrKxLrNC9H@google.com>
On Wed, 2026-08-12 at 17:16 -0700, Sean Christopherson wrote:
> > > I think this blurb came from Sean, but can we standardize on "TDX module"?
> > > The
> > > code currently uses "TDX module" and "TDX-module" and "TDX-module" used
> > > much
> > > less. I also don't see why it needs the "-".
>
> FWIW, I like TDX-Module to clearly identify it as _the_ TDX-Module, versus a
> potential TDX module provided the kernel, i.e. a tdx.ko module.
Hmm, I see your point. I'm on board with taking that as the new target. I say we
just pick something to go forward with for future changes, and be consistent. We
can put fixing up the old non-conforming ones as a very low priority cleanup for
the future.
next prev parent reply other threads:[~2026-08-13 18:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 11:21 [PATCH v2 0/3] KVM: TDX: Enable VM-DoS Prevention Features for TDX Xiaoyao Li
2026-08-10 11:21 ` [PATCH v2 1/3] KVM: TDX: Enable Notify VM exit Xiaoyao Li
2026-08-11 0:37 ` Edgecombe, Rick P
2026-08-10 11:21 ` [PATCH v2 2/3] KVM: TDX: Fix the exit reason handling Xiaoyao Li
2026-08-11 0:03 ` Sean Christopherson
2026-08-11 3:17 ` Xiaoyao Li
2026-08-11 17:36 ` Sean Christopherson
2026-08-11 0:38 ` Edgecombe, Rick P
2026-08-11 1:32 ` Xiaoyao Li
2026-08-11 15:20 ` Edgecombe, Rick P
2026-08-12 7:29 ` Xiaoyao Li
2026-08-12 20:21 ` Edgecombe, Rick P
2026-08-13 0:16 ` Sean Christopherson
2026-08-13 8:34 ` Xiaoyao Li
2026-08-13 18:19 ` Edgecombe, Rick P [this message]
2026-08-10 11:22 ` [PATCH v2 3/3] KVM: TDX: Enable Bus Lock VM exit Xiaoyao Li
2026-08-11 1:18 ` Edgecombe, Rick P
2026-08-11 1:44 ` 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=c2093dc50d2603c90fd40c7544561eb95d017898.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