diff options
author | Mark Rutland | 2015-01-15 17:42:14 +0100 |
---|---|---|
committer | Catalin Marinas | 2015-01-16 17:21:58 +0100 |
commit | 6083fe74b7bfffc2c7be8c711596608bda0cda6e (patch) | |
tree | 2a7b9401b1d12ff52ee38645f8156a91a6c4cccf /arch/arm64/include | |
parent | arm64/efi: handle potential failure to remap memory map (diff) | |
download | kernel-qcow2-linux-6083fe74b7bfffc2c7be8c711596608bda0cda6e.tar.gz kernel-qcow2-linux-6083fe74b7bfffc2c7be8c711596608bda0cda6e.tar.xz kernel-qcow2-linux-6083fe74b7bfffc2c7be8c711596608bda0cda6e.zip |
arm64: respect mem= for EFI
When booting with EFI, we acquire the EFI memory map after parsing the
early params. This unfortuantely renders the option useless as we call
memblock_enforce_memory_limit (which uses memblock_remove_range behind
the scenes) before we've added any memblocks. We end up removing
nothing, then adding all of memory later when efi_init calls
reserve_regions.
Instead, we can log the limit and apply this later when we do the rest
of the memblock work in memblock_init, which should work regardless of
the presence of EFI. At the same time we may as well move the early
parameter into arm64's mm/init.c, close to arm64_memblock_init.
Any memory which must be mapped (e.g. for use by EFI runtime services)
must be mapped explicitly reather than relying on the linear mapping,
which may be truncated as a result of a mem= option passed on the kernel
command line.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Leif Lindholm <leif.lindholm@linaro.org>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'arch/arm64/include')
0 files changed, 0 insertions, 0 deletions