summaryrefslogtreecommitdiffstats
path: root/drivers/firmware/broadcom
diff options
context:
space:
mode:
authorArd Biesheuvel <ardb@kernel.org>2020-03-31 10:59:39 +0200
committerArd Biesheuvel <ardb@kernel.org>2020-04-24 14:52:16 +0200
commite71356fe29e7bd5cd5e07800d4940a7481fb0854 (patch)
tree6af50c284f6fb7a76d0aa38217b5b50b1e63079d /drivers/firmware/broadcom
parent43b1df0e013c25abb536699f46d0e9f291b586a0 (diff)
downloadlinux-e71356fe29e7bd5cd5e07800d4940a7481fb0854.tar.gz
linux-e71356fe29e7bd5cd5e07800d4940a7481fb0854.tar.bz2
linux-e71356fe29e7bd5cd5e07800d4940a7481fb0854.zip
efi/libstub/arm64: Switch to ordinary page allocator for kernel image
It is no longer necessary to locate the kernel as low as possible in physical memory, and so we can switch from efi_low_alloc() [which is a rather nasty concoction on top of GetMemoryMap()] to a new helper called efi_allocate_pages_aligned(), which simply rounds up the size to account for the alignment, and frees the misaligned pages again. So considering that the kernel can live anywhere in the physical address space, as long as its alignment requirements are met, let's switch to efi_allocate_pages_aligned() to allocate the pages. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'drivers/firmware/broadcom')
0 files changed, 0 insertions, 0 deletions