diff options
| author | Laszlo Ersek <lersek@redhat.com> | 2019-09-20 17:07:43 +0200 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2020-02-05 12:59:32 +0000 |
| commit | adec2bd598dac8a6378d6244089158ed8d656f62 (patch) | |
| tree | bd0d632ebb2518ae65201de9f8dff4bb682d30d6 /BaseTools/Source/Python/AutoGen/AutoGenWorker.py | |
| parent | 73974f809cbfc2b4cecec539b2eb8635b0e42eff (diff) | |
| download | edk2-adec2bd598dac8a6378d6244089158ed8d656f62.tar.gz edk2-adec2bd598dac8a6378d6244089158ed8d656f62.tar.bz2 edk2-adec2bd598dac8a6378d6244089158ed8d656f62.zip | |
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>
Diffstat (limited to 'BaseTools/Source/Python/AutoGen/AutoGenWorker.py')
0 files changed, 0 insertions, 0 deletions