linux-coco.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Tom Dohrmann <erbse.13@gmx.de>
To: Tom Lendacky <thomas.lendacky@amd.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 draft specification v0.62 / GHCB draft specification v2.03
Date: Thu, 16 Mar 2023 21:31:11 +0100	[thread overview]
Message-ID: <ZBN8jz867HNLHVuj@notebook> (raw)
In-Reply-To: <a2f31400-9e1c-c12a-ad7f-ea0265a12068@amd.com>

On Tue, Mar 14, 2023 at 05:08:17PM -0500, Tom Lendacky wrote:
> Attached is an updated draft version of the SVSM specification with feedback
> incorporated from the previous review.
>
> Also attached is a draft GHCB specification with updates for APIC ID
> retrieval and VMPL/VMSA level execution (and an SEV-ES enhancement to use
> the SNP Page State Change support for working with UPM).

AFAICT the new GHCB spec explains how to run a vCPU at another VMPL,
but doesn't contain any information about how to registers a new VMSA
for a specific VMPL. From looking at some of the patches used for SVSM
it seems that a new field in the AP Creation NAE was added, but the
specification wasn't yet updated accordingly.

Regards,
Tom

> Please take a look and reply with any feedback you may have.
>
> Thanks,
> Tom




  reply	other threads:[~2023-03-16 20:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 22:08 SVSM draft specification v0.62 / GHCB draft specification v2.03 Tom Lendacky
2023-03-16 20:31 ` Tom Dohrmann [this message]
2023-03-16 21:12   ` Tom Lendacky
2023-03-17 16:49     ` Tom Lendacky
2023-04-17 17:07       ` 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=ZBN8jz867HNLHVuj@notebook \
    --to=erbse.13@gmx.de \
    --cc=amd-sev-snp@lists.suse.com \
    --cc=linux-coco@lists.linux.dev \
    --cc=thomas.lendacky@amd.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).