public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Lendacky, Thomas" <thomas.lendacky@amd.com>
To: Michael Roth <michael.roth@amd.com>, devel@edk2.groups.io
Cc: "Ni, Ray" <ray.ni@intel.com>
Subject: Re: [PATCH v3 0/4] Fix AP Jump Table Handling for SEV-SNP
Date: Mon, 23 May 2022 08:58:47 -0500	[thread overview]
Message-ID: <a02f1e13-80e6-2ec5-6d4f-08f9f3294160@amd.com> (raw)
In-Reply-To: <20220520152730.7924-1-michael.roth@amd.com>

On 5/20/22 10:27, Michael Roth wrote:
> A full-featured SEV-SNP guest will not rely on the AP jump table, and
> will instead use the AP Creation interface defined by the GHCB. However,
> a guest is still allowed to use the AP jump table if desired.
> 
> However, unlike with SEV-ES guests, SEV-SNP guests should not
> store/retrieve the jump table address via GHCB requests to the
> hypervisor, they should instead store/retrieve it via the SEV-SNP
> secrets page.
> 
> This series implements the store side of this for OVMF by introducing a
> PCD that can be used to pass the SEV-SNP secrets page address to
> UefiCpuPkg, where the jump table address is allocated. It also
> introduces a struct that defines the SEV-SNP secrets page format
> according to the GHCB v2.01 and SEV-SNP FW ABI specifications.
> 
> v3:
>   - Break up single patch into a set of patches containing the specific
>     changes for each package. (Ray)
> 
> v2:
>   - Update Secrets OS area to match latest GHCB 2.01 spec (Tom)
>   - Move Secrets header file into ./Register/AMD subdirectory (Tom)
>   - Fix CI EccCheck due to assignment in variable declaration

Aside from the minor comment on patch 4, for the series:

Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>

> 
>   MdePkg/Include/Register/Amd/SnpSecretsPage.h  | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>   MdePkg/MdePkg.dec                             |  4 ++++
>   OvmfPkg/AmdSev/AmdSevX64.dsc                  |  3 +++
>   OvmfPkg/CloudHv/CloudHvX64.dsc                |  3 +++
>   OvmfPkg/IntelTdx/IntelTdxX64.dsc              |  3 +++
>   OvmfPkg/Microvm/MicrovmX64.dsc                |  3 +++
>   OvmfPkg/OvmfPkgIa32.dsc                       |  3 +++
>   OvmfPkg/OvmfPkgIa32X64.dsc                    |  3 +++
>   OvmfPkg/OvmfPkgX64.dsc                        |  3 +++
>   OvmfPkg/PlatformPei/AmdSev.c                  |  5 +++++
>   OvmfPkg/PlatformPei/PlatformPei.inf           |  1 +
>   UefiCpuPkg/Library/MpInitLib/DxeMpInitLib.inf |  1 +
>   UefiCpuPkg/Library/MpInitLib/DxeMpLib.c       | 10 ++++++++++
>   13 files changed, 98 insertions(+)
> 
> 

      parent reply	other threads:[~2022-05-23 13:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 15:27 [PATCH v3 0/4] Fix AP Jump Table Handling for SEV-SNP Michael Roth
2022-05-20 15:27 ` [PATCH v3 1/4] MdePkg: Add header for SEV-SNP secrets page struct Michael Roth
2022-05-20 15:27 ` [PATCH v3 2/4] MdePkg: Add PcdSevSnpSecretsAddress to export SEV-SNP secrets page Michael Roth
2022-05-20 15:27 ` [PATCH v3 3/4] OvmfPkg: Initialize the PcdSevSnpSecretsAddress PCD during PEI phase Michael Roth
2022-05-20 15:27 ` [PATCH v3 4/4] UefiCpuPkg: Store SEV-SNP AP jump table in the secrets page Michael Roth
2022-05-23 13:57   ` Lendacky, Thomas
2022-05-23 13:58 ` Lendacky, Thomas [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-list 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=a02f1e13-80e6-2ec5-6d4f-08f9f3294160@amd.com \
    --to=devel@edk2.groups.io \
    /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