• Mark Rutland's avatar
    arm64: respect mem= for EFI · 6083fe74
    Mark Rutland authored
    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
    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: default avatarMark Rutland <mark.rutland@arm.com>
    Acked-by: default avatarCatalin Marinas <catalin.marinas@arm.com>
    Acked-by: default avatarArd Biesheuvel <ard.biesheuvel@linaro.org>
    Tested-by: default avatarArd Biesheuvel <ard.biesheuvel@linaro.org>
    Cc: Leif Lindholm <leif.lindholm@linaro.org>
    Cc: Will Deacon <will.deacon@arm.com>
    Signed-off-by: default avatarCatalin Marinas <catalin.marinas@arm.com>
setup.c 13.2 KB