From: Tom Lendacky <thomas.lendacky@amd.com>
To: Dionna Amalie Glaze <dionnaglaze@google.com>
Cc: "linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"amd-sev-snp@lists.suse.com" <amd-sev-snp@lists.suse.com>
Subject: Re: SVSM Attestation and vTPM specification additions - v0.60
Date: Tue, 10 Jan 2023 15:03:02 -0600 [thread overview]
Message-ID: <804079b5-c090-af4b-ecca-839ab8bea0f7@amd.com> (raw)
In-Reply-To: <CAAH4kHa_DN2e4DreB_PfUEsu7KrB64=m5=-HnH+WpnmecoRz3g@mail.gmail.com>
On 1/10/23 13:40, Dionna Amalie Glaze wrote:
> typo: "oridnal"
Will fix.
>
> For the statement "Locality usage for the vTPM is not currently
> defined." should this be interpreted as version 1 of the vTPM protocol
> will not support locality, or simply that version 1 might have the
> affordance to add behavior for non-zero locality in a future revision
> of version 1, such that the result is not specified as
> SVSM_ERR_INVALID_PARAMETER? I think the latter is probably a dangerous
> interpretation unless v0.60 of this document is strictly considered
> "unstable" and shouldn't be used upstream, so I'd recommend clarifying
> that "currently" in a document that might later be outdated should be
> precise about its specified behavior in a versioned fashion.
Version 1 of the vTPM protocol will not support locality, so I'll remove
the "currently." If locality is to be supported, it would be in a post
version 1 of the vTPM protocol and will likely require invoking a new call
id (unless we somehow manage to figure out locality before v1.0 of the
SVSM specification).
v0.60 of the SVSM specification is not to be used upstream. Once v1.0 is
reached, then it can be considered stable for usage upstream.
Thanks for the feedback.
Tom
>
> On Tue, Jan 10, 2023 at 10:54 AM Tom Lendacky <thomas.lendacky@amd.com> wrote:
>>
>> Attached is an updated draft version of the SVSM specification with added
>> support for an attestation protocol and a vTPM protocol as well as other
>> miscellaneous changes (all identified by change bar). Please take a look
>> and reply with any feedback you may have.
>>
>> Thanks,
>> Tom
>
>
>
next prev parent reply other threads:[~2023-01-10 21:03 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 18:54 SVSM Attestation and vTPM specification additions - v0.60 Tom Lendacky
2023-01-10 19:37 ` Tom Lendacky
2023-01-10 19:40 ` Dionna Amalie Glaze
2023-01-10 21:03 ` Tom Lendacky [this message]
2023-01-10 22:14 ` James Bottomley
2023-01-10 22:45 ` Tom Lendacky
2023-01-10 23:52 ` James Bottomley
2023-01-11 9:15 ` Christophe de Dinechin Dupont de Dinechin
2023-01-10 20:29 ` James Bottomley
2023-01-10 20:37 ` James Bottomley
2023-01-10 21:33 ` Tom Lendacky
2023-01-10 21:32 ` Tom Lendacky
2023-01-10 21:47 ` James Bottomley
2023-01-10 23:00 ` Tom Lendacky
2023-01-10 23:09 ` James Bottomley
2023-01-11 14:49 ` Tom Lendacky
2023-01-11 14:56 ` James Bottomley
2023-01-10 23:14 ` James Bottomley
2023-01-11 16:39 ` Christophe de Dinechin
2023-01-11 23:00 ` Tom Lendacky
2023-01-12 1:27 ` [EXTERNAL] " Jon Lange
2023-01-13 16:10 ` Tom Lendacky
2023-01-12 13:57 ` James Bottomley
2023-01-12 15:13 ` Tom Lendacky
2023-01-12 15:24 ` James Bottomley
2023-01-13 16:12 ` Tom Lendacky
2023-01-12 8:19 ` Dov Murik
2023-01-12 12:18 ` James Bottomley
2023-01-13 16:16 ` Tom Lendacky
2023-01-13 11:50 ` Nicolai Stange
2023-01-13 17:20 ` Tom Lendacky
2023-01-24 9:35 ` Jörg Rödel
2023-01-26 14:36 ` Tom Lendacky
2023-01-26 16:45 ` Christophe de Dinechin Dupont de Dinechin
2023-02-01 10:50 ` Jörg Rödel
2023-02-20 15:10 ` Tom Lendacky
2023-01-24 9:45 ` Jörg Rödel
2023-01-26 14:51 ` Tom Lendacky
2023-01-26 16:49 ` Christophe de Dinechin Dupont de Dinechin
2023-01-26 17:33 ` [EXTERNAL] " Jon Lange
2023-01-27 8:35 ` Jörg Rödel
2023-01-27 16:11 ` Jon Lange
2023-01-30 11:29 ` Jörg Rödel
2023-01-31 4:44 ` Jon Lange
2023-01-31 15:06 ` Tom Lendacky
2023-01-31 15:34 ` Jon Lange
2023-02-01 15:20 ` [EXTERNAL] " Christophe de Dinechin Dupont de Dinechin
2023-02-02 6:04 ` Jon Lange
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=804079b5-c090-af4b-ecca-839ab8bea0f7@amd.com \
--to=thomas.lendacky@amd.com \
--cc=amd-sev-snp@lists.suse.com \
--cc=dionnaglaze@google.com \
--cc=linux-coco@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).