From: <dan.j.williams@intel.com>
To: Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Kiryl Shutsemau <kas@kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-coco@lists.linux.dev>
Subject: Re: [PATCH v1 3/3] virt: tdx-guest: Increase Quote buffer size to 128KB
Date: Wed, 11 Feb 2026 13:06:17 -0800 [thread overview]
Message-ID: <698cef4964e8_8c32100a3@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <6983882c-2c00-42f4-924b-5fb3619840be@linux.intel.com>
Kuppuswamy Sathyanarayanan wrote:
> Hi Kiryl,
>
> Thanks for the review!
>
> On 2/11/2026 3:17 AM, Kiryl Shutsemau wrote:
> > On Tue, Feb 10, 2026 at 04:17:12PM -0800, Kuppuswamy Sathyanarayanan wrote:
> >> Intel platforms are transitioning from traditional SGX-based
> >> attestation toward DICE-based attestation as part of a broader move
> >> toward open and standardized attestation models. DICE enables layered
> >> and extensible attestation, where evidence is accumulated across
> >> multiple boot stages.
> >>
> >> With SGX-based attestation, Quote sizes are typically under 8KB, as the
> >> payload consists primarily of Quote data and a small certificate bundle.
> >> Existing TDX guest code sizes the Quote buffer accordingly.
> >>
> >> DICE-based attestation produces significantly larger Quotes due to the
> >> inclusion of evidence (certificate chains) from multiple boot layers.
> >> The cumulative Quote size can reach approximately 100KB.
> >>
> >> Increase GET_QUOTE_BUF_SIZE to 128KB to ensure sufficient buffer
> >> capacity for DICE-based Quote payloads.
> >
> > It worth noting that it requires guest physically-contiguous memory.
> >
> > Single order-5 allocation is not that bad as long as the driver
> > initialized during the boot.
>
> Good point! We can add following to the commit log:
>
> The Quote buffer requires guest physically-contiguous memory and is
> allocated once during driver initialization at boot time, where an
> order-5 allocation (128KB) is expected to succeed reliably.
That is good feedback. I would rather not restart the timer on the
linux-next exposure with a rebase to add that. I think in this case it
is sufficient that the commit has a link back to this discussion:
Link: https://patch.msgid.link/20260211001712.1531955-4-sathyanarayanan.kuppuswamy@linux.intel.com
However, when the the patch to add the link to the documentation for the
CBOR Web Token schema is ready, do take the opportunity to also add a
patch commenting about the order-5 allocation risk to
GET_QUOTE_BUF_SIZE.
Later, when / if these objects start to get into order-10+ allocations
for PQC etc, a scatter-gather mechanism will need to be considered.
next prev parent reply other threads:[~2026-02-11 21:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 0:17 [PATCH v1 0/3] Increase CoCo attestation report buffer size Kuppuswamy Sathyanarayanan
2026-02-11 0:17 ` [PATCH v1 1/3] virt: tsm: Document size limits for outblob attributes Kuppuswamy Sathyanarayanan
2026-02-11 2:15 ` dan.j.williams
2026-02-11 16:40 ` Kuppuswamy Sathyanarayanan
2026-02-11 20:48 ` dan.j.williams
2026-02-11 0:17 ` [PATCH v1 2/3] virt: tsm: Increase TSM_REPORT_OUTBLOB_MAX to 16MB Kuppuswamy Sathyanarayanan
2026-02-11 2:16 ` dan.j.williams
2026-02-11 0:17 ` [PATCH v1 3/3] virt: tdx-guest: Increase Quote buffer size to 128KB Kuppuswamy Sathyanarayanan
2026-02-11 2:19 ` dan.j.williams
2026-02-11 11:17 ` Kiryl Shutsemau
2026-02-11 18:40 ` Kuppuswamy Sathyanarayanan
2026-02-11 21:06 ` dan.j.williams [this message]
2026-02-11 21:13 ` Kuppuswamy Sathyanarayanan
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=698cef4964e8_8c32100a3@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kas@kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=x86@kernel.org \
/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