From: "Ni, Ray" <ray.ni@intel.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>
Cc: "Dong, Eric" <eric.dong@intel.com>,
"Kumar, Rahul R" <rahul.r.kumar@intel.com>,
Michael Roth <michael.roth@amd.com>,
Ashish Kalra <Ashish.Kalra@amd.com>
Subject: Re: [edk2-devel] [PATCH v2 0/2] SEV-SNP guest support fixes
Date: Fri, 31 Mar 2023 07:32:26 +0000 [thread overview]
Message-ID: <MN6PR11MB824493C6438BB98A488159A28C8F9@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
In-Reply-To: <torjqygabjq3mhpldzips7vpfv5yte5242jeks2zps7gix4jv2@nn2hvvck4uk3>
Acked-by: Ray Ni <ray.ni@intel.com>
> -----Original Message-----
> From: Gerd Hoffmann <kraxel@redhat.com>
> Sent: Thursday, March 30, 2023 3:36 PM
> To: devel@edk2.groups.io; thomas.lendacky@amd.com
> Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; Kumar, Rahul R <rahul.r.kumar@intel.com>; Michael
> Roth <michael.roth@amd.com>; Ashish Kalra <Ashish.Kalra@amd.com>
> Subject: Re: [edk2-devel] [PATCH v2 0/2] SEV-SNP guest support fixes
>
> On Tue, Mar 28, 2023 at 01:09:22PM -0500, Lendacky, Thomas via groups.io wrote:
> > This patch series provides some fixes around AP creation:
> >
> > - An erratum on AMD hardware requires that a VMSA not be aligned on a
> > 2MB boundary. To work around this issue, allocate 2 pages of memory
> > and using the page that is not 2MB aligned and freeing the other.
> >
> > - When parking APs after exiting boot services, the current SNP support
> > will perform an allocation that will not be reflected in memory map
> > being supplied to the OS. Instead of allocating new VMSAs each time,
> > re-use the current VMSA.
> >
> > BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=4353
> >
> > ---
> >
> > Changes since v1:
> > - Change the order of the patches to make the patch diffs easier
> > to review
> > - Add erratum number to the patch description and code comment
> > - Use existing ALIGN_POINTER macro
>
> Series:
> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
>
> take care,
> Gerd
prev parent reply other threads:[~2023-03-31 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 18:09 [PATCH v2 0/2] SEV-SNP guest support fixes Lendacky, Thomas
2023-03-28 18:09 ` [PATCH v2 1/2] UefiCpuPkg/MpInitLib: Reuse VMSA allocation to avoid unreserved allocation Lendacky, Thomas
2023-03-28 18:09 ` [PATCH v2 2/2] UefiCpuPkg/MpInitLib: Ensure SEV-SNP VMSA allocations are not 2MB aligned Lendacky, Thomas
[not found] ` <1750A7A753390E6E.29160@groups.io>
2023-03-28 18:20 ` [edk2-devel] " Lendacky, Thomas
2023-03-30 7:36 ` [edk2-devel] [PATCH v2 0/2] SEV-SNP guest support fixes Gerd Hoffmann
2023-03-31 7:32 ` Ni, Ray [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=MN6PR11MB824493C6438BB98A488159A28C8F9@MN6PR11MB8244.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