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
This commit is contained in:
Jordan Justen 2014-01-30 01:06:47 +00:00 committed by jljusten
parent c3cf8daa0f
commit 8d25bed4bd
1 changed files with 2 additions and 2 deletions

View File

@ -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
);
//