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 <jordan.l.justen@intel.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Bill Paul <wpaul@windriver.com>
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 fbdb597043ec5a124d5422c65b1484b3e339e796..1ee417a091dbd3a9693a84df5a7999597d448ea3 100644 (file)
--- a/OvmfPkg/PlatformPei/Fv.c
+++ b/OvmfPkg/PlatformPei/Fv.c
@@ -36,12 +36,12 @@ PeiFvInitialization (
   //\r
   // Create a memory allocation HOB for the PEI FV.\r
   //\r
-  // This is marked as ACPI NVS so it will still be available on S3 resume.\r
+  // Note: This should be changed to ACPI NVS when S3 resume is enabled.\r
   //\r
   BuildMemoryAllocationHob (\r
     PcdGet32 (PcdOvmfPeiMemFvBase),\r
     PcdGet32 (PcdOvmfPeiMemFvSize),\r
-    EfiACPIMemoryNVS\r
+    EfiBootServicesData\r
     );\r
 \r
   //\r