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>
Cc: Tom Dohrmann <erbse.13@gmx.de>
Subject: Re: SVSM draft specification v0.62 / GHCB draft specification v2.03
Date: Mon, 17 Apr 2023 12:07:06 -0500 [thread overview]
Message-ID: <a4b8da44-89d3-c34b-f1cf-8d247835b4f7@amd.com> (raw)
In-Reply-To: <8391bd0a-9a3e-d572-234c-e43f4ba47d0c@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]
On 3/17/23 11:49, Tom Lendacky wrote:
> On 3/16/23 16:12, Tom Lendacky wrote:
>> On 3/16/23 15:31, Tom Dohrmann wrote:
>>> 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.
>>
>> Ah, you are correct. I missed pulling that change into this version of
>> the document. Thanks for pointing that out.
Attached is the updated GHCB specification with the previously missing
changes required for creating non-zero VMPL APs.
Thanks,
Tom
>
> And just as an FYI until the next draft, bit positions 16-19 of
> SW_EXITINFO1 on the AP Create NAE event will indicate the VMPL for which
> the VMSA is being created/deleted.
>
> Thanks,
> Tom
>
>>
>> Thanks,
>> Tom
>>
>>>
>>> Regards,
>>> Tom
>>>
>>>> Please take a look and reply with any feedback you may have.
>>>>
>>>> Thanks,
>>>> Tom
>>>
>>>
>>>
[-- Attachment #2: 56421-Guest_Hypervisor_Communication_Block_Standardization-v2.03.pdf --]
[-- Type: application/pdf, Size: 1041679 bytes --]
prev parent reply other threads:[~2023-04-17 17:07 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
2023-03-16 21:12 ` Tom Lendacky
2023-03-17 16:49 ` Tom Lendacky
2023-04-17 17:07 ` Tom Lendacky [this message]
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=a4b8da44-89d3-c34b-f1cf-8d247835b4f7@amd.com \
--to=thomas.lendacky@amd.com \
--cc=amd-sev-snp@lists.suse.com \
--cc=erbse.13@gmx.de \
--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).