From: Peter Fang <peter.fang@intel.com>
To: "Reshetova, Elena" <elena.reshetova@intel.com>
Cc: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"seanjc@google.com" <seanjc@google.com>,
"Xu, Yilun" <yilun.xu@intel.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"Annapurve, Vishal" <vannapurve@google.com>,
"kas@kernel.org" <kas@kernel.org>,
"Wu, Binbin" <binbin.wu@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: TDG quote analysis
Date: Wed, 23 Sep 2026 15:50:18 -0700 [thread overview]
Message-ID: <arRXqpG_4hCrhQLM@intel.com> (raw)
In-Reply-To: <DS4PPFA84FA90FC61E43D50956C3226AA02E7822@DS4PPFA84FA90FC.namprd11.prod.outlook.com>
On Wed, Sep 23, 2026 at 01:50:17AM -0700, Reshetova, Elena wrote:
>
> > On Tue, 2026-09-22 at 06:48 +0000, Reshetova, Elena wrote:
> > > Hope this clarifies how to calculate memory impact.
> >
> > Sean is suggesting to have some save state area per-TD such that each TD can
> > get
> > a quote without interfering with the other. I think this is saying inside TDX
> > module you need a "vCPU" and a "session", at which point you can execute
> > independently from the other quotes. Together that would take:
> >
A recap of the PUCK meeting discussion today:
1. The TDG quoting idea would make things simpler for the host, but at
the cost of chunking up and disturbing crypto primitives. So in the
end we all agreed to keep the original TDH direction.
2. Use concurrent TDH quoting threads (number of physical cores).
3. Punt on the S3M-based quoting for now.
4. Use the existing mechanisms (polling or async notification) to handle
quoting completion.
Please feel free to correct or add to this. Thanks all for the feedback!
prev parent reply other threads:[~2026-09-23 22:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 0:48 TDG quote analysis Edgecombe, Rick P
2026-09-16 18:00 ` Sean Christopherson
2026-09-16 18:49 ` Edgecombe, Rick P
2026-09-16 19:27 ` Sean Christopherson
2026-09-16 22:31 ` Edgecombe, Rick P
2026-09-16 23:00 ` Peter Fang
2026-09-16 23:57 ` Sean Christopherson
2026-09-17 0:56 ` Edgecombe, Rick P
2026-09-17 13:37 ` Sean Christopherson
2026-09-17 18:12 ` Edgecombe, Rick P
2026-09-17 19:57 ` Sean Christopherson
2026-09-17 21:32 ` Edgecombe, Rick P
2026-09-18 0:04 ` Sean Christopherson
2026-09-18 2:39 ` Edgecombe, Rick P
2026-09-18 13:13 ` Sean Christopherson
2026-09-18 18:12 ` Edgecombe, Rick P
2026-09-18 21:32 ` Sean Christopherson
2026-09-21 23:00 ` Peter Fang
2026-09-21 23:06 ` Dave Hansen
2026-09-23 4:09 ` Vishal Annapurve
2026-09-24 0:03 ` Vishal Annapurve
2026-09-24 0:18 ` Sean Christopherson
2026-09-24 0:44 ` Edgecombe, Rick P
2026-09-24 16:28 ` Sean Christopherson
2026-09-21 23:04 ` Dave Hansen
2026-09-21 23:19 ` Sean Christopherson
2026-09-21 23:36 ` Dave Hansen
2026-09-21 23:46 ` Sean Christopherson
2026-09-22 0:03 ` Dave Hansen
2026-09-22 6:48 ` Reshetova, Elena
2026-09-22 17:07 ` Edgecombe, Rick P
2026-09-23 8:50 ` Reshetova, Elena
2026-09-23 22:50 ` Peter Fang [this message]
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=arRXqpG_4hCrhQLM@intel.com \
--to=peter.fang@intel.com \
--cc=binbin.wu@intel.com \
--cc=dave.hansen@intel.com \
--cc=elena.reshetova@intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=vannapurve@google.com \
--cc=yilun.xu@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