diff options
author | Ard Biesheuvel <ardb@kernel.org> | 2022-11-22 18:02:49 +0100 |
---|---|---|
committer | Will Deacon <will@kernel.org> | 2022-11-25 12:20:12 +0000 |
commit | 453dfcee70c5c344ca09396ff5b0baf177eb327e (patch) | |
tree | 6a8eb86defece40d853d32c8406831cfa335b198 /arch/arm64 | |
parent | 0bb1fbffc631064db567ccaeb9ed6b6df6342b66 (diff) | |
download | linux-453dfcee70c5c344ca09396ff5b0baf177eb327e.tar.bz2 |
arm64: booting: Require placement within 48-bit addressable memory
Some configurations (i.e., 64k + LVA/LPA) can tolerate a physical
placement of the kernel image outside of the 48-bit addressable region,
but given that the loader has no way of knowing whether or not the image
in question supports LVA/LPA, it currently has no choice but to place it
below the 48-bit mark.
Once we add support for LPA2, which allows 52-bit physical and virtual
addressing when using 4k or 16k pages, but in way that relies on
increasing the number of paging levels, there will be more variety in
the configurations that may or may not support this.
So redefine bit #3 in the Image header as 'must be placed within 48-bit
addressable memory', as this is the current de facto meaning.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Link: https://lore.kernel.org/r/20221122170249.2453853-1-ardb@kernel.org
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'arch/arm64')
0 files changed, 0 insertions, 0 deletions