From: Jason Gunthorpe <jgg@nvidia.com>
To: "Reshetova, Elena" <elena.reshetova@intel.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
"Jiang, Dave" <dave.jiang@intel.com>,
Xu Yilun <yilun.xu@linux.intel.com>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
Jiri Pirko <jiri@resnulli.us>,
"Tian, Kevin" <kevin.tian@intel.com>,
Alexey Kardashevskiy <aik@amd.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Steven Price <steven.price@arm.com>,
Kiryl Shutsemau <kas@kernel.org>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Jonathan Cameron <jic23@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Ashish Kalra <ashish.kalra@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
John Allen <john.allen@amd.com>, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
Alistair <alistair23@gmail.com>
Subject: Re: [RFC PATCH v1 10/11] virt: coco: arm-cca-host: Publish slot zero and establish streams after acceptance
Date: Fri, 20 Nov 2026 09:55:46 -0400 [thread overview]
Message-ID: <20261120135546.GV2245175@nvidia.com> (raw)
In-Reply-To: <DS4PPFA84FA90FC5CBC7769BB1213B1724FE7782@DS4PPFA84FA90FC.namprd11.prod.outlook.com>
On Fri, Nov 20, 2026 at 01:01:28PM +0000, Reshetova, Elena wrote:
>
> > > > > And this is where in our original SPDM_DEVICE_ATTESTATION_INFO_T
> > > > > struct VCA should have lived instead of being a separate structure with
> > digest.
> > > > > Would that be acceptable?
> > > >
> > > > I'm not sure what you are proposing?
> > > >
> > > > My concern is you have this digest over a struct that isn't a protocol
> > > > struct, so we have to make a special API to pass your special struct.
> > > >
> > > > Unless we can get rid of that I don't know if I care what you put in
> > > > the struct, but the kernel will have to break it up and your driver
> > > > will be more complicated than it needed to be.
> > >
> > > I am trying to see how break this struct the best. And the only open
> > > question I have so far is where to plug VCA (rest is clear).
> >
> > ARM has it nearly right, VCA is captured in plain text as the session
> > transcript. This TSM directed capture primitive is what you need for
> > 1.3 because we want to capture GET_DIGESTS and then pause.
>
> Small question here: why does the host need to capture
> GET_DIGESTS given that we trust TSM to verify the transcript and
> integrity of provided cert chains to the host?
We need the slot mask in the OS to present to the uAPI so we can know
what slots are valid to fetch certificates for. DIGESTS is the message
that has it. This all has to be done before telling the TSM what the
slot is, before key exchange.
Yes you can make this more convoluted by having more TSM API surface
for the TSM to report things already in plaintext messages, but that
does not seem good from a TCB perspective, plus it means every TSM
would have various bits of unique code to do these entirely standard
things.
> > > What is the usecase for this given we have above 3 items?
> >
> > The one you mentioned, single evidence collection. If the device is in
> > "TSM Controlled nonce" mode then the host can make a single
> > collection and present it to the guest over and over again.
>
> So, you mean here like "initial device attestation evidence at the
> SPDM connect establishment time"?
I don't want the TSM to have any opinion when the evidence is
collected. The OS/user will decide when this happens. If OS wants it
to be 'initial' then it can ask for it them.
> If yes, then I think TSM controlled nonce is misleading, i.e. it is
> not about nonce, it is about the time when evidence was collected.
> And do you plan to support this model in Linux?
It starts with the nonce, if we want to mess with the collection time
the first issue is the guest cannot supply a nonce. We can't trust the
host to provide a nonce, so it must come from the TSM.
If the TSM provides a nonce then there is a host based command to get
a new TSM nonce and perform an evidence collection. Obviously we need
to offer a way to freshen the evidence if the user so desires.
The userspace should control when the VDEV's digests visible to the
guest get updated. The host decides when this happens, but it must not
do it asynchronously from the guest's perspective otherwise there are
unsolvable races.
Yes, the feature seems to be about controlling the time of evidence
collection, but the actual mechanism is giving the TSM control over
the nonce.
I still don't know if that is what that user wants, hopefully we will
have more clarity soon.
Jason
next prev parent reply other threads:[~2026-11-20 13:55 UTC|newest]
Thread overview: 127+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 15:26 [RFC PATCH v1 00/11] PCI/TSM: Add CTLV attestation Aneesh Kumar K.V (Arm)
2026-10-28 15:26 ` [RFC PATCH v1 01/11] attestation: Restrict inherited operations per instance Aneesh Kumar K.V (Arm)
2026-10-30 13:29 ` Jiri Pirko
2026-10-28 15:26 ` [RFC PATCH v1 02/11] attestation: Filter evidence objects " Aneesh Kumar K.V (Arm)
2026-10-30 13:44 ` Jiri Pirko
2026-10-31 6:24 ` Aneesh Kumar K.V
2026-11-02 19:14 ` Jiri Pirko
2026-10-28 15:26 ` [RFC PATCH v1 03/11] attestation: Enter secure operation when evidence is accepted Aneesh Kumar K.V (Arm)
2026-10-30 13:51 ` Jiri Pirko
2026-10-30 15:36 ` Jason Gunthorpe
2026-10-31 4:09 ` Aneesh Kumar K.V
2026-11-02 11:28 ` Jiri Pirko
2026-10-28 15:26 ` [RFC PATCH v1 04/11] attestation: Bind object selection to accepted evidence snapshots Aneesh Kumar K.V (Arm)
2026-10-28 15:26 ` [RFC PATCH v1 05/11] attestation: Make the evidence-get challenge attribute optional Aneesh Kumar K.V (Arm)
2026-10-28 15:26 ` [RFC PATCH v1 06/11] PCI/TSM: Describe the PCI attestation control family Aneesh Kumar K.V (Arm)
2026-10-30 14:01 ` Jiri Pirko
2026-10-30 15:43 ` Jason Gunthorpe
2026-11-02 12:45 ` Jiri Pirko
2026-11-03 15:45 ` Jason Gunthorpe
2026-11-04 9:21 ` Jiri Pirko
2026-11-04 14:00 ` Jason Gunthorpe
2026-10-31 4:05 ` Aneesh Kumar K.V
2026-11-02 11:50 ` Jiri Pirko
2026-11-03 15:35 ` Jason Gunthorpe
2026-10-31 4:22 ` Aneesh Kumar K.V
2026-11-02 11:30 ` Jiri Pirko
2026-11-03 15:39 ` Jason Gunthorpe
2026-10-28 15:26 ` [RFC PATCH v1 07/11] attestation: Add attestation helpers for PCI/TSM integration Aneesh Kumar K.V (Arm)
2026-10-28 15:26 ` [RFC PATCH v1 08/11] PCI/TSM: Bind CTLV attestation to connected and locked contexts Aneesh Kumar K.V (Arm)
2026-10-28 22:56 ` Dave Jiang
2026-10-29 5:30 ` Aneesh Kumar K.V
2026-10-29 12:41 ` Jason Gunthorpe
2026-10-30 14:04 ` Jiri Pirko
2026-10-30 14:08 ` Jiri Pirko
2026-10-30 15:39 ` Jason Gunthorpe
2026-11-02 12:11 ` Jiri Pirko
2026-11-03 15:41 ` Jason Gunthorpe
2026-10-28 15:26 ` [RFC PATCH v1 09/11] crypto/ccp: Defer SEV-TIO link setup until evidence acceptance Aneesh Kumar K.V (Arm)
2026-11-06 7:47 ` Alexey Kardashevskiy
2026-11-06 13:14 ` Aneesh Kumar K.V
2026-11-06 14:21 ` Jason Gunthorpe
2026-11-09 10:03 ` Alexey Kardashevskiy
2026-11-12 6:23 ` Aneesh Kumar K.V
2026-10-28 15:26 ` [RFC PATCH v1 10/11] virt: coco: arm-cca-host: Publish slot zero and establish streams after acceptance Aneesh Kumar K.V (Arm)
2026-10-29 16:56 ` Dave Jiang
2026-10-29 17:10 ` Jason Gunthorpe
2026-10-30 9:58 ` Reshetova, Elena
2026-10-30 13:15 ` Jason Gunthorpe
2026-10-31 3:47 ` Aneesh Kumar K.V
2026-11-02 10:11 ` Reshetova, Elena
2026-11-02 17:26 ` Jason Gunthorpe
2026-11-03 12:01 ` Reshetova, Elena
2026-11-03 15:16 ` Jason Gunthorpe
2026-11-04 8:03 ` Xu Yilun
2026-11-04 9:49 ` Reshetova, Elena
2026-11-04 13:41 ` Jason Gunthorpe
2026-11-04 16:54 ` Dave Jiang
2026-11-06 15:53 ` Dave Jiang
2026-11-06 19:30 ` Jason Gunthorpe
2026-11-06 22:39 ` Dave Jiang
2026-11-08 18:33 ` Jason Gunthorpe
2026-11-09 10:55 ` Reshetova, Elena
2026-11-09 13:47 ` Jason Gunthorpe
2026-11-09 17:37 ` Dave Jiang
2026-11-09 18:53 ` Jason Gunthorpe
2026-11-09 20:54 ` Dave Jiang
2026-11-09 23:40 ` Jason Gunthorpe
2026-11-10 13:15 ` Reshetova, Elena
2026-11-10 14:20 ` Jason Gunthorpe
2026-11-11 13:09 ` Reshetova, Elena
2026-11-11 14:13 ` Jason Gunthorpe
2026-11-12 1:48 ` Alexey Kardashevskiy
2026-11-12 12:31 ` Jason Gunthorpe
2026-11-17 0:48 ` Alexey Kardashevskiy
2026-11-17 1:18 ` Jason Gunthorpe
2026-11-18 11:12 ` Alexey Kardashevskiy
2026-11-18 13:41 ` Jason Gunthorpe
2026-11-19 2:19 ` Alexey Kardashevskiy
2026-11-19 14:03 ` Jason Gunthorpe
2026-11-10 1:40 ` Alistair
2026-11-10 15:07 ` Jason Gunthorpe
2026-11-17 23:12 ` Alistair Francis
2026-11-18 0:33 ` Jason Gunthorpe
2026-11-10 5:32 ` Alexey Kardashevskiy
2026-11-10 12:52 ` Jason Gunthorpe
2026-11-11 9:03 ` Alexey Kardashevskiy
2026-11-12 9:37 ` Aneesh Kumar K.V
2026-11-12 14:52 ` Jason Gunthorpe
2026-11-12 15:47 ` Dave Jiang
2026-11-12 16:37 ` Jason Gunthorpe
2026-11-13 8:54 ` Aneesh Kumar K.V
2026-11-13 14:52 ` Jason Gunthorpe
2026-11-13 16:29 ` Aneesh Kumar K.V
2026-11-13 19:06 ` Jason Gunthorpe
2026-11-13 16:38 ` Aneesh Kumar K.V
2026-11-13 19:12 ` Jason Gunthorpe
2026-11-13 17:12 ` Aneesh Kumar K.V
2026-11-13 19:34 ` Jason Gunthorpe
2026-11-16 13:38 ` Reshetova, Elena
2026-11-16 14:33 ` Jason Gunthorpe
2026-11-17 13:00 ` Reshetova, Elena
2026-11-17 14:20 ` Jason Gunthorpe
2026-11-18 11:12 ` Alexey Kardashevskiy
2026-11-18 13:16 ` Jason Gunthorpe
2026-11-19 2:19 ` Alexey Kardashevskiy
2026-11-19 14:00 ` Jason Gunthorpe
2026-11-18 12:26 ` Reshetova, Elena
2026-11-18 13:38 ` Jason Gunthorpe
2026-11-20 13:01 ` Reshetova, Elena
2026-11-20 13:55 ` Jason Gunthorpe [this message]
2026-11-17 11:17 ` Alexey Kardashevskiy
2026-11-17 13:28 ` Jason Gunthorpe
2026-11-10 20:07 ` Jason Gunthorpe
2026-11-04 9:03 ` Reshetova, Elena
2026-11-04 13:48 ` Jason Gunthorpe
2026-11-06 8:24 ` Aneesh Kumar K.V
2026-11-06 12:49 ` Reshetova, Elena
2026-11-06 15:53 ` Aneesh Kumar K.V
2026-11-06 18:54 ` Jason Gunthorpe
2026-11-03 16:31 ` Aneesh Kumar K.V
2026-11-03 17:56 ` Jason Gunthorpe
2026-11-02 10:05 ` Reshetova, Elena
2026-11-02 10:22 ` Reshetova, Elena
2026-11-02 17:37 ` Jason Gunthorpe
2026-10-28 15:26 ` [RFC PATCH v1 11/11] virt: coco: arm-cca-guest: Refresh selected evidence against trusted digests Aneesh Kumar K.V (Arm)
2026-10-30 12:34 ` [RFC PATCH v1 00/11] PCI/TSM: Add CTLV attestation Xu Yilun
2026-10-30 15:32 ` Jason Gunthorpe
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=20261120135546.GV2245175@nvidia.com \
--to=jgg@nvidia.com \
--cc=aik@amd.com \
--cc=alistair23@gmail.com \
--cc=aneesh.kumar@kernel.org \
--cc=ashish.kalra@amd.com \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=elena.reshetova@intel.com \
--cc=jic23@kernel.org \
--cc=jiri@resnulli.us \
--cc=john.allen@amd.com \
--cc=kas@kernel.org \
--cc=kevin.tian@intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=patches@lists.linux.dev \
--cc=rick.p.edgecombe@intel.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=thomas.lendacky@amd.com \
--cc=will@kernel.org \
--cc=yilun.xu@linux.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.