From: Peter Fang <peter.fang@intel.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Li, Xiaoyao" <xiaoyao.li@intel.com>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"kas@kernel.org" <kas@kernel.org>,
"seanjc@google.com" <seanjc@google.com>,
"binbin.wu@linux.intel.com" <binbin.wu@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"tony.lindgren@linux.intel.com" <tony.lindgren@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"tglx@kernel.org" <tglx@kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"Bityutskiy, Artem" <artem.bityutskiy@intel.com>,
"sathyanarayanan.kuppuswamy@linux.intel.com"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v4 0/4] tdx-guest: Make Quote buffer size dynamic
Date: Tue, 15 Sep 2026 17:50:15 -0700 [thread overview]
Message-ID: <aqnnx3aNjeDzobaq@intel.com> (raw)
In-Reply-To: <b32cd186709b93a02495a1efcb347f8f9533b510.camel@intel.com>
On Tue, Sep 15, 2026 at 05:36:49PM -0700, Edgecombe, Rick P wrote:
> On Tue, 2026-09-15 at 17:34 -0700, Peter Fang wrote:
> > > Is it all correct?
> >
> > Yes. If a new TDX module decides to report this field on a non-DICE
> > platform, this code still works [1].
>
> So the real scenario is TDX on a DICE platform, while using legacy SGX based
> attestation?
Yes that is the real scenario and this series supports it. Reporting
this field on a non-DICE platform is just a theory at this point.
This is probably pretty obvious... This series still only uses the
GetQuote GHCI for quoting, so there is no other future DICE enabling in
it.
>
> > And quotes in the DICE world will
> > continue to get larger. This metadata reporting is useful regardless of
> > how DICE is implemented in the end. I wanted to be upfront about what
> > the potential impact may be if the guest did DICE differently. The guest
> > would still need this reported size from the TDX module.
> >
> > [1] https://lore.kernel.org/kvm/apsxN4jYe3G3meNz@intel.com/
>
next prev parent reply other threads:[~2026-09-16 0:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 9:25 [PATCH v4 0/4] tdx-guest: Make Quote buffer size dynamic Peter Fang
2026-09-15 9:26 ` [PATCH v4 1/4] x86/tdx: Add helper to query maximum TD Quote size Peter Fang
2026-09-21 22:14 ` Dave Hansen
2026-09-22 16:06 ` Peter Fang
2026-09-15 9:26 ` [PATCH v4 2/4] virt: tdx-guest: Calculate the Quote buffer size safely Peter Fang
2026-09-16 12:26 ` Kiryl Shutsemau
2026-09-15 9:26 ` [PATCH v4 3/4] virt: tdx-guest: Use a variable to store the Quote buffer size Peter Fang
2026-09-16 12:30 ` Kiryl Shutsemau
2026-09-22 10:05 ` Xiaoyao Li
2026-09-22 14:59 ` Dave Hansen
2026-09-22 16:30 ` Peter Fang
2026-09-22 17:34 ` Dave Hansen
2026-09-22 21:36 ` Peter Fang
2026-09-22 21:40 ` Dave Hansen
2026-09-22 19:46 ` Edgecombe, Rick P
2026-09-22 22:38 ` Dave Hansen
2026-09-15 9:26 ` [PATCH v4 4/4] virt: tdx-guest: Allocate Quote buffer dynamically Peter Fang
2026-09-16 12:31 ` Kiryl Shutsemau
2026-09-17 9:23 ` Peter Fang
2026-09-21 22:47 ` Dave Hansen
2026-09-22 16:20 ` Peter Fang
2026-09-15 14:07 ` [PATCH v4 0/4] tdx-guest: Make Quote buffer size dynamic Sean Christopherson
2026-09-15 16:11 ` Edgecombe, Rick P
2026-09-15 23:04 ` Peter Fang
2026-09-16 0:06 ` Edgecombe, Rick P
2026-09-16 0:34 ` Peter Fang
2026-09-16 0:36 ` Edgecombe, Rick P
2026-09-16 0:50 ` Peter Fang [this message]
2026-09-16 1:20 ` 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=aqnnx3aNjeDzobaq@intel.com \
--to=peter.fang@intel.com \
--cc=artem.bityutskiy@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=seanjc@google.com \
--cc=tglx@kernel.org \
--cc=tony.lindgren@linux.intel.com \
--cc=x86@kernel.org \
--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 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.