From: Tom Lendacky <thomas.lendacky@amd.com>
To: "linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"amd-sev-snp@lists.suse.com" <amd-sev-snp@lists.suse.com>
Subject: SVSM draft specification now available
Date: Wed, 21 Sep 2022 12:13:58 -0500 [thread overview]
Message-ID: <3aa30eef-408e-33ba-b0d6-c3ecac7ad27e@amd.com> (raw)
All,
A link to the draft SVSM specification can be found at
https://developer.amd.com/sev/ or you can find it directly at
https://developer.amd.com/wp-content/resources/58019.pdf.
Please read through it and lets start discussing it and what changes might
be required for the first version (which could include additional
protocols and/or functions, e.g. vTPM support).
Thanks,
Tom
reply other threads:[~2022-09-21 17:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3aa30eef-408e-33ba-b0d6-c3ecac7ad27e@amd.com \
--to=thomas.lendacky@amd.com \
--cc=amd-sev-snp@lists.suse.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 read-only IMAP folder(s) and NNTP newsgroup(s).