From: Jordan Justen Date: Thu, 30 Jan 2014 01:06:47 +0000 (+0000) Subject: OvmfPkg/PlatformPei: Don't allocate ACPI NVS memory X-Git-Tag: edk2-stable201903~11759 X-Git-Url: https://git.proxmox.com/?p=mirror_edk2.git;a=commitdiff_plain;h=8d25bed4bd18daff0b7151e47542b5edd0467fd7 OvmfPkg/PlatformPei: Don't allocate ACPI NVS memory Once we support ACPI S3, then we can restore this to being allocated as ACPI NVS memory. At that time we should also have a way to disable S3 support in QEMU. When we detect that S3 is disabled in QEMU, then we can allocate this as regular Boot Services Data memory. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Jordan Justen Reviewed-by: Laszlo Ersek Reviewed-by: Bill Paul git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@15198 6f19259b-4bc3-4df7-8a09-765794883524 --- diff --git a/OvmfPkg/PlatformPei/Fv.c b/OvmfPkg/PlatformPei/Fv.c index fbdb597043..1ee417a091 100644 --- a/OvmfPkg/PlatformPei/Fv.c +++ b/OvmfPkg/PlatformPei/Fv.c @@ -36,12 +36,12 @@ PeiFvInitialization ( // // Create a memory allocation HOB for the PEI FV. // - // This is marked as ACPI NVS so it will still be available on S3 resume. + // Note: This should be changed to ACPI NVS when S3 resume is enabled. // BuildMemoryAllocationHob ( PcdGet32 (PcdOvmfPeiMemFvBase), PcdGet32 (PcdOvmfPeiMemFvSize), - EfiACPIMemoryNVS + EfiBootServicesData ); //