From: Dov Murik <dovmurik@linux.ibm.com>
To: linux-coco@lists.linux.dev
Cc: Dov Murik <dovmurik@linux.ibm.com>,
Tobin Feldman-Fitzthum <tobin@linux.ibm.com>,
James Bottomley <jejb@linux.ibm.com>,
Claudio Carvalho <cclaudio@linux.ibm.com>
Subject: [RFC PATCH 0/3] Retrieve SNP attestation from SVSM
Date: Wed, 7 Jun 2023 18:06:43 +0300 [thread overview]
Message-ID: <20230607150646.97208-1-dovmurik@linux.ibm.com> (raw)
This is an initial attempt to allow userspace to fetch attestation
report from SVSM on SNP. It was tested with AMD's linux-svsm to which
we added support for the attestation protocol. The kernel patches in
this series only expose the SVSM_ATTEST_SERVICES function, for now.
The request for the attestation report is exposed to userspace as a new
ioctl call (SNP_SVSM_ATTEST_SERVICES) on /dev/sev-guest. It returns the
VMPL0 attestation report, the services manifest, and the host
certificate chain, according to the SVSM spec.
Note that the existing SNP_GET_REPORT and SNP_GET_EXT_REPORT calls still
work under SVSM, as long as a VMPL1 report is requested.
This series should be applied on top of AMD's SVSM guest tree:
https://github.com/AMDESE/linux/tree/svsm-preview-guest
The SVSM code which supports the attestation protocol is in:
https://github.com/svsm-vtpm/linux-svsm/tree/attestation-protocol-v2
(as of writing, it hasn't yet been merged to AMD's linux-svsm.)
Dov Murik (3):
x86/sev: Add __svsm_msr_protocol_2() which returns register values
x86/sev: Add snp_svsm_attest_services()
virt: sevguest: Add support to get attestation report from SVSM
arch/x86/include/asm/sev.h | 26 ++++++++
arch/x86/kernel/sev-shared.c | 49 ++++++++++++++
arch/x86/kernel/sev.c | 46 +++++++++++++
drivers/virt/coco/sevguest/sevguest.c | 95 +++++++++++++++++++++++++++
include/uapi/linux/sev-guest.h | 34 ++++++++++
5 files changed, 250 insertions(+)
--
2.35.3
next reply other threads:[~2023-06-07 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 15:06 Dov Murik [this message]
2023-06-07 15:06 ` [RFC PATCH 1/3] x86/sev: Add __svsm_msr_protocol_2() which returns register values Dov Murik
2023-06-07 15:06 ` [RFC PATCH 2/3] x86/sev: Add snp_svsm_attest_services() Dov Murik
2023-06-07 15:06 ` [RFC PATCH 3/3] virt: sevguest: Add support to get attestation report from SVSM Dov Murik
2023-06-07 16:23 ` Daniel P. Berrangé
2023-06-07 17:05 ` Dov Murik
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=20230607150646.97208-1-dovmurik@linux.ibm.com \
--to=dovmurik@linux.ibm.com \
--cc=cclaudio@linux.ibm.com \
--cc=jejb@linux.ibm.com \
--cc=linux-coco@lists.linux.dev \
--cc=tobin@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).