]> git.proxmox.com Git - mirror_edk2.git/commit
OvmfPkg/PlatformPei: assert there's no permanent PEI RAM at default SMBASE
authorLaszlo Ersek <lersek@redhat.com>
Fri, 20 Sep 2019 15:07:43 +0000 (17:07 +0200)
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Wed, 5 Feb 2020 12:59:32 +0000 (12:59 +0000)
commitadec2bd598dac8a6378d6244089158ed8d656f62
treebd0d632ebb2518ae65201de9f8dff4bb682d30d6
parent73974f809cbfc2b4cecec539b2eb8635b0e42eff
OvmfPkg/PlatformPei: assert there's no permanent PEI RAM at default SMBASE

The permanent PEI RAM that is published on the normal boot path starts
strictly above MEMFD_BASE_ADDRESS (8 MB -- see the FDF files), regardless
of whether PEI decompression will be necessary on S3 resume due to
SMM_REQUIRE. Therefore the normal boot permanent PEI RAM never overlaps
with the SMRAM at the default SMBASE (192 KB).

The S3 resume permanent PEI RAM is strictly above the normal boot one.
Therefore the no-overlap statement holds true on the S3 resume path as
well.

Assert the no-overlap condition commonly for both boot paths in
PublishPeiMemory().

Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=1512
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Jiewen Yao <jiewen.yao@intel.com>
Message-Id: <20200129214412.2361-7-lersek@redhat.com>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
OvmfPkg/PlatformPei/MemDetect.c