public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: Michael Roth <michael.roth@amd.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	"Ni, Ray" <ray.ni@intel.com>, Gerd Hoffmann <kraxel@redhat.com>,
	"Aktas, Erdem" <erdemaktas@google.com>,
	James Bottomley <jejb@linux.ibm.com>,
	"Xu, Min M" <min.m.xu@intel.com>
Subject: Re: [PATCH v2 0/4] Fixes for SEV-SNP CC blob and CPUID table handling
Date: Wed, 26 Apr 2023 14:22:28 +0000	[thread overview]
Message-ID: <MW4PR11MB5872C7B599FFDCACD0509DA98C659@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230425203258.255583-1-michael.roth@amd.com>

Merged https://github.com/tianocore/edk2/pull/4313

> -----Original Message-----
> From: Michael Roth <michael.roth@amd.com>
> Sent: Wednesday, April 26, 2023 4:33 AM
> To: devel@edk2.groups.io
> Cc: Ard Biesheuvel <ardb@kernel.org>; Tom Lendacky
> <thomas.lendacky@amd.com>; Yao, Jiewen <jiewen.yao@intel.com>; Ni,
> Ray <ray.ni@intel.com>; Gerd Hoffmann <kraxel@redhat.com>; Aktas,
> Erdem <erdemaktas@google.com>; James Bottomley <jejb@linux.ibm.com>;
> Xu, Min M <min.m.xu@intel.com>
> Subject: [PATCH v2 0/4] Fixes for SEV-SNP CC blob and CPUID table handling
> 
> (Mainly a resend of v1, but rolled in Gerd's Acked-by's, addressed
> new coding style check in the CI, and updated Cc list)
> 
> Here are a number of fixes related to OVMF handling of the SEV-SNP
> Confidential Computing blob and CPUID table.
> 
> Patch #1 is a fix for recently-reported issue that can cause
> significant problems with some SEV-SNP guest operating systems.
> Please consider applying this patch directly if the other
> patches in this series are held up for any reason.
> 
> Patches 2-4 are minor changes for things that aren't currently
> triggered in practice, but make OVMF's SEV-SNP implementation more
> robust for different build/hypervisor environments in the future.
> Patch #2 was submitted previously, but refreshed here to apply
> cleanly on top of Patch #1, with no other functional changes since
> the initial review.
> 
> v2:
>  - rebased/retested on latest master
>  - replaced usage of __FUNCTION__ with __func__ to comply with new CI
>    test cases
> 
> ----------------------------------------------------------------
> Michael Roth (4):
>       OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC blob as
> EfiACPIReclaimMemory
>       OvmfPkg/AmdSevDxe: Update ConfidentialComputing blob struct
> definition
>       OvmfPkg/CcExitLib: Fix SEV-SNP XSave area size calculation
>       OvmfPkg/CcExitLib: Use documented XSave area base size for SEV-SNP
> 
>  OvmfPkg/AmdSevDxe/AmdSevDxe.c                          | 64
> ++++++++++++++++++++++++++++++++++++++++++++++++++--------------
>  OvmfPkg/Include/Guid/ConfidentialComputingSevSnpBlob.h |  6 ++++--
>  OvmfPkg/Library/CcExitLib/CcExitVcHandler.c            | 13 +++++--------
>  3 files changed, 59 insertions(+), 24 deletions(-)
> 


      parent reply	other threads:[~2023-04-26 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 20:32 [PATCH v2 0/4] Fixes for SEV-SNP CC blob and CPUID table handling Roth, Michael
2023-04-25 20:32 ` [PATCH v2 1/4] OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC blob as EfiACPIReclaimMemory Roth, Michael
2023-04-25 20:32 ` [PATCH v2 2/4] OvmfPkg/AmdSevDxe: Update ConfidentialComputing blob struct definition Roth, Michael
2023-04-25 20:32 ` [PATCH v2 3/4] OvmfPkg/CcExitLib: Fix SEV-SNP XSave area size calculation Roth, Michael
2023-04-25 20:32 ` [PATCH v2 4/4] OvmfPkg/CcExitLib: Use documented XSave area base size for SEV-SNP Roth, Michael
2023-04-26 14:22 ` Yao, Jiewen [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=MW4PR11MB5872C7B599FFDCACD0509DA98C659@MW4PR11MB5872.namprd11.prod.outlook.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