From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: Michael Roth <michael.roth@amd.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
"Ni, Ray" <ray.ni@intel.com>,
"Ard Biesheuvel" <ardb+tianocore@kernel.org>,
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 0/4] Fixes for SEV-SNP CC blob and CPUID table handling
Date: Wed, 18 Jan 2023 03:57:12 +0000 [thread overview]
Message-ID: <MW4PR11MB5872F7CA87530B1EDBDF18BA8CC79@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221221174130.xbi6q3irva6kcitx@amd.com>
Hi Roth
I got weird merge conflict when I try to apply the patches from email.
Would you please resubmit the patch based on latest code base?
Once I see the new version, I will try to merge them again.
Thank you
Yao, Jiewen
> -----Original Message-----
> From: Michael Roth <michael.roth@amd.com>
> Sent: Thursday, December 22, 2022 1:42 AM
> To: devel@edk2.groups.io
> Cc: Tom Lendacky <thomas.lendacky@amd.com>; Ni, Ray
> <ray.ni@intel.com>; Ard Biesheuvel <ardb+tianocore@kernel.org>; Yao,
> Jiewen <jiewen.yao@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 0/4] Fixes for SEV-SNP CC blob and CPUID table handling
>
> On Wed, Dec 21, 2022 at 10:06:47AM -0600, Michael Roth wrote:
> > 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.
> >
> > ----------------------------------------------------------------
> > 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
>
> Adding some Cc's from Maintainers.txt that I should have included
> originally:
>
> Ard Biesheuvel <ardb+tianocore@kernel.org>
> Jiewen Yao <jiewen.yao@intel.com>
> Gerd Hoffmann <kraxel@redhat.com>
> Erdem Aktas <erdemaktas@google.com>
> James Bottomley <jejb@linux.ibm.com>
> Min Xu <min.m.xu@intel.com>
>
> Thanks,
>
> Mike
>
> >
> > OvmfPkg/AmdSevDxe/AmdSevDxe.c | 64
> ++++++++++++++++++++++++++++++++++----------
> > OvmfPkg/Include/Guid/ConfidentialComputingSevSnpBlob.h | 6 +++--
> > OvmfPkg/Library/CcExitLib/CcExitVcHandler.c | 13 ++++-----
> > 3 files changed, 59 insertions(+), 24 deletions(-)
> >
> >
prev parent reply other threads:[~2023-01-18 3:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 16:06 [PATCH 0/4] Fixes for SEV-SNP CC blob and CPUID table handling Roth, Michael
2022-12-21 16:06 ` [PATCH 1/4] OvmfPkg/AmdSevDxe: Allocate SEV-SNP CC blob as EfiACPIReclaimMemory Roth, Michael
2022-12-21 16:48 ` Lendacky, Thomas
2022-12-21 21:26 ` Dov Murik
2023-01-06 9:18 ` [edk2-devel] " Yao, Jiewen
2023-01-06 20:25 ` Dov Murik
2023-01-07 2:01 ` Yao, Jiewen
2023-01-07 16:52 ` Ard Biesheuvel
2023-01-12 10:15 ` Yao, Jiewen
2022-12-21 16:06 ` [PATCH 2/4] OvmfPkg/AmdSevDxe: Update ConfidentialComputing blob struct definition Roth, Michael
2023-01-06 9:14 ` [edk2-devel] " Yao, Jiewen
2022-12-21 16:06 ` [PATCH 3/4] OvmfPkg/CcExitLib: Fix SEV-SNP XSave area size calculation Roth, Michael
2022-12-21 16:52 ` Lendacky, Thomas
2023-01-06 8:53 ` [edk2-devel] " Yao, Jiewen
2022-12-21 16:06 ` [PATCH 4/4] OvmfPkg/CcExitLib: Use documented XSave area base size for SEV-SNP Roth, Michael
2022-12-21 16:59 ` Lendacky, Thomas
2023-01-06 8:53 ` [edk2-devel] " Yao, Jiewen
2022-12-21 17:41 ` [PATCH 0/4] Fixes for SEV-SNP CC blob and CPUID table handling Roth, Michael
2023-01-18 3:57 ` 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=MW4PR11MB5872F7CA87530B1EDBDF18BA8CC79@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