linux-coco.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Tom Lendacky <thomas.lendacky@amd.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org,
	linux-coco@lists.linux.dev, svsm-devel@coconut-svsm.dev
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andy Lutomirski <luto@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Michael Roth <michael.roth@amd.com>,
	Ashish Kalra <ashish.kalra@amd.com>
Subject: Re: [PATCH v5 12/13] x86/sev: Extend the config-fs attestation support for an SVSM
Date: Thu, 6 Jun 2024 14:15:38 -0500	[thread overview]
Message-ID: <f00f2767-c113-0953-9869-c9696da677f0@amd.com> (raw)
In-Reply-To: <965015dce3c76bb8724839d50c5dea4e4b5d598f.1717600736.git.thomas.lendacky@amd.com>

On 6/5/24 10:18, Tom Lendacky wrote:
> When an SVSM is present, the guest can also request attestation reports
> from the SVSM. These SVSM attestation reports can be used to attest the
> SVSM and any services running within the SVSM.
> 
> Extend the config-fs attestation support to allow for an SVSM attestation
> report. This involves creating four (4) new config-fs attributes:
> 
>    - 'service-provider' (input)
>      This attribute is used to determine whether the attestation request
>      should be sent to the specified service provider or to the SEV
>      firmware. The SVSM service provider is represented by the value
>      'svsm'.
> 
>    - 'service_guid' (input)
>      Used for requesting the attestation of a single service within the
>      service provider. A null GUID implies that the SVSM_ATTEST_SERVICES
>      call should be used to request the attestation report. A non-null
>      GUID implies that the SVSM_ATTEST_SINGLE_SERVICE call should be used.
> 
>    - 'service_manifest_version' (input)
>      Used with the SVSM_ATTEST_SINGLE_SERVICE call, the service version
>      represents a specific service manifest version be used for the
>      attestation report.
> 
>    - 'manifestblob' (output)
>      Used to return the service manifest associated with the attestation
>      report.
> 
> Only display these new attributes when running under an SVSM.
> 
> Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
>   Documentation/ABI/testing/configfs-tsm  |  63 +++++++++
>   arch/x86/include/asm/sev.h              |  31 ++++-
>   arch/x86/kernel/sev.c                   |  50 +++++++
>   drivers/virt/coco/sev-guest/sev-guest.c | 178 ++++++++++++++++++++++++
>   drivers/virt/coco/tsm.c                 |  93 ++++++++++++-
>   include/linux/tsm.h                     |  19 +++
>   6 files changed, 431 insertions(+), 3 deletions(-)
> 

Here's a small change to provide better error detail that you can squash
into this patch if that's ok.

Thanks,
Tom

diff --git a/drivers/virt/coco/sev-guest/sev-guest.c b/drivers/virt/coco/sev-guest/sev-guest.c
index 655865164705..e32ac31e0630 100644
--- a/drivers/virt/coco/sev-guest/sev-guest.c
+++ b/drivers/virt/coco/sev-guest/sev-guest.c
@@ -886,7 +886,8 @@ static int sev_svsm_report_new(struct tsm_report *report, void *data)
  
  			return -EINVAL;
  		default:
-			pr_err_ratelimited("SVSM attestation request failed (%#x)\n", ret);
+			pr_err_ratelimited("SVSM attestation request failed (%d / 0x%llx)\n",
+					   ret, call.rax_out);
  			return -EINVAL;
  		}
  	}

  reply	other threads:[~2024-06-06 19:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 15:18 [PATCH v5 00/13] Provide SEV-SNP support for running under an SVSM Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 01/13] x86/irqflags: Provide native versions of the local_irq_save()/restore() Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 02/13] x86/sev: Check for the presence of an SVSM in the SNP Secrets page Tom Lendacky
2024-06-05 19:38   ` Borislav Petkov
2024-06-05 21:17     ` Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 03/13] x86/sev: Use kernel provided SVSM Calling Areas Tom Lendacky
2024-06-06 12:36   ` Borislav Petkov
2024-06-05 15:18 ` [PATCH v5 04/13] x86/sev: Perform PVALIDATE using the SVSM when not at VMPL0 Tom Lendacky
2024-06-06 14:38   ` Borislav Petkov
2024-06-17 17:50   ` Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 05/13] x86/sev: Use the SVSM to create a vCPU when not in VMPL0 Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 06/13] x86/sev: Provide SVSM discovery support Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 07/13] x86/sev: Provide guest VMPL level to userspace Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 08/13] virt: sev-guest: Choose the VMPCK key based on executing VMPL Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 09/13] configfs-tsm: Allow the privlevel_floor attribute to be updated Tom Lendacky
2024-06-14 20:47   ` Dan Williams
2024-06-05 15:18 ` [PATCH v5 10/13] fs/configfs: Add a callback to determine attribute visibility Tom Lendacky
2024-07-11 20:07   ` Christophe JAILLET
2024-06-05 15:18 ` [PATCH v5 11/13] x86/sev: Take advantage of configfs visibility support in TSM Tom Lendacky
2024-06-05 15:18 ` [PATCH v5 12/13] x86/sev: Extend the config-fs attestation support for an SVSM Tom Lendacky
2024-06-06 19:15   ` Tom Lendacky [this message]
2024-06-05 15:18 ` [PATCH v5 13/13] x86/sev: Allow non-VMPL0 execution when an SVSM is present Tom Lendacky

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=f00f2767-c113-0953-9869-c9696da677f0@amd.com \
    --to=thomas.lendacky@amd.com \
    --cc=ashish.kalra@amd.com \
    --cc=bp@alien8.de \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=michael.roth@amd.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=svsm-devel@coconut-svsm.dev \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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).