[PATCH v2 0/3] support reserving crashkernel above 4G on arm64 kdump
chenzhou10 at huawei.com
Tue Apr 9 00:31:40 PDT 2019
When crashkernel is reserved above 4G in memory, kernel should reserve
some amount of low memory for swiotlb and some DMA buffers. So there may
be two crash kernel regions, one is below 4G, the other is above 4G.
Crash dump kernel reads more than one crash kernel regions via a dtb
property under node /chosen,
linux,usable-memory-range = <BASE1 SIZE1 [BASE2 SIZE2]>.
Besides, we need to modify kexec-tools:
arm64: support more than one crash kernel regions(see )
Changes since [v1]:
- Move common reserve_crashkernel_low() code into kernel/kexec_core.c.
- Remove memblock_cap_memory_ranges() i added in v1 and implement that
There are at most two crash kernel regions, for two crash kernel regions
case, we cap the memory range [min(regs[*].start), max(regs[*].end)]
and then remove the memory range in the middle.
Chen Zhou (3):
arm64: kdump: support reserving crashkernel above 4G
arm64: kdump: support more than one crash kernel regions
kdump: update Documentation about crashkernel on arm64
Documentation/admin-guide/kernel-parameters.txt | 4 +-
arch/arm64/include/asm/kexec.h | 3 +
arch/arm64/kernel/setup.c | 3 +
arch/arm64/mm/init.c | 92 +++++++++++++++++++++----
arch/x86/include/asm/kexec.h | 3 +
arch/x86/kernel/setup.c | 66 ++----------------
include/linux/kexec.h | 1 +
include/linux/memblock.h | 6 ++
kernel/kexec_core.c | 53 ++++++++++++++
mm/memblock.c | 7 +-
10 files changed, 159 insertions(+), 79 deletions(-)
More information about the kexec