diff options
author | Ard Biesheuvel <ard.biesheuvel@linaro.org> | 2018-12-07 11:27:32 +0100 |
---|---|---|
committer | Ard Biesheuvel <ard.biesheuvel@linaro.org> | 2018-12-20 11:01:38 +0100 |
commit | 67b8f806d22abfe9c16ec8b29a8d19885298ba1d (patch) | |
tree | 74e3d1fe686a65774dac9075aff25f3171f57257 /BaseTools/Source/Python/Workspace/MetaFileParser.py | |
parent | 5c8bc8be9e5e4665ab7e31558db9e3fe9990a13e (diff) | |
download | edk2-67b8f806d22abfe9c16ec8b29a8d19885298ba1d.tar.gz edk2-67b8f806d22abfe9c16ec8b29a8d19885298ba1d.tar.bz2 edk2-67b8f806d22abfe9c16ec8b29a8d19885298ba1d.zip |
MdePkg/Base: introduce MAX_ALLOC_ADDRESS
On some architectures, the maximum representable address deviates from
the virtual address range that is accessible by the firmware at boot
time. For instance, on AArch64, UEFI mandates a 4 KB page size, which
limits the address space to 48 bits, while more than that may be
populated on a particular platform, for use by the OS.
So introduce a new macro MAX_ALLOC_ADDRESS, which represent the maximum
address the firmware should take into account when allocating memory
ranges that need to be accessible by the CPU at boot time.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Liming Gao <liming.gao@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/Workspace/MetaFileParser.py')
0 files changed, 0 insertions, 0 deletions