summaryrefslogtreecommitdiffstats
path: root/arch/m68k
diff options
context:
space:
mode:
authorMatt Fleming <matt@codeblueprint.co.uk>2016-06-22 16:54:00 +0100
committerMatt Fleming <matt@codeblueprint.co.uk>2016-09-09 16:07:47 +0100
commitc45f4da33a297f85435f8dccb26a24852ea01bb9 (patch)
tree3bf0927904747a9b36b57058e1dce31e87f87dab /arch/m68k
parent60863c0d1a96b740048cc7d94a2d00d6f89ba3d8 (diff)
downloadop-kernel-dev-c45f4da33a297f85435f8dccb26a24852ea01bb9.zip
op-kernel-dev-c45f4da33a297f85435f8dccb26a24852ea01bb9.tar.gz
efi: Add efi_memmap_install() for installing new EFI memory maps
While efi_memmap_init_{early,late}() exist for architecture code to install memory maps from firmware data and for the virtual memory regions respectively, drivers don't care which stage of the boot we're at and just want to swap the existing memmap for a modified one. efi_memmap_install() abstracts the details of how the new memory map should be mapped and the existing one unmapped. Tested-by: Dave Young <dyoung@redhat.com> [kexec/kdump] Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> [arm] Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Cc: Leif Lindholm <leif.lindholm@linaro.org> Cc: Peter Jones <pjones@redhat.com> Cc: Borislav Petkov <bp@alien8.de> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Taku Izumi <izumi.taku@jp.fujitsu.com> Signed-off-by: Matt Fleming <matt@codeblueprint.co.uk>
Diffstat (limited to 'arch/m68k')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud