arm64: support more than one crash kernel regions
Subsystems (2)
PATCH v5 1/1 arm64: support more than one crash kernel regions
From: Chen Zhou <[email protected]>
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.
Currently, there is only one crash kernel region on arm64, and pass "linux,usable-memory-range = <BASE SIZE>" property to crash dump kernel.
Now, we pass "linux,usable-memory-range = <BASE1 SIZE1 BASE2 SIZE2>" to crash dump kernel to support two crash kernel regions and load crash kernel high. Make the low memory region as the second range "BASE2 SIZE2" to keep compatibility with existing user-space and older kdump kernels.
--- kexec/arch/arm64/crashdump-arm64.c | 44 +++++++++------- kexec/arch/arm64/crashdump-arm64.h | 5 +- kexec/arch/arm64/kexec-arm64.c | 84 ++++++++++++++++++++---------- 3 files changed, 86 insertions(+), 47 deletions(-)
Changes since [v4]:
1. Repalce "Crash kernel (low)" with "Crash kernel", consistent with the x86 implementation. See:
e25e6e7593ca ("kdump, x86: Process multiple Crash kernel in /proc/iomem")
2. Expand fdt_setprop_range() to fdt_setprop_ranges() instead of adding the latter. Parameter 'reverse' is added to control whether to reversely output data to fdt.
Changes since [v3]:
- Reuse DT property "linux,usable-memory-range". Reuse DT property "linux,usable-memory-range" to pass the low memory region.
Changes since [v2]:
- Rebase to latest kexec-tools code.
Changes since [v1]:
- Add another DT property "linux,low-memory-range" to crash dump kernel's dtb to pass the low region instead of reusing "linux,usable-memory-range".
[1]: http://lists.infradead.org/pipermail/kexec/2019-April/022792.html
[2]: http://lists.infradead.org/pipermail/kexec/2019-August/023569.html
[3]: http://lists.infradead.org/pipermail/kexec/2020-May/025128.html
[4]: http://lists.infradead.org/pipermail/kexec/2020-June/020737.html
kexec/arch/arm64/crashdump-arm64.c +26 -18
@@ -27,11 +27,11 @@static struct memory_ranges system_memory_rgns;/* memory range reserved for crashkernel */ -struct memory_range crash_reserved_mem; +struct memory_range crash_reserved_mem[CRASH_MAX_RESERVED_RANGES ];struct memory_ranges usablemem_rgns = { .size =0 , - .max_size =1 , - .ranges = &crash_reserved_mem, + .max_size =CRASH_MAX_RESERVED_RANGES , + .ranges = crash_reserved_mem, };struct memory_range elfcorehdr_mem;
@@ -111,7 +111,7 @@ int is_crashkernel_mem_reserved(void)if (!usablemem_rgns.size)kexec_iomem_for_each_line (NULL , iomem_range_callback,NULL ); -return crash_reserved_mem.start != crash_reserved_mem.end; +return usablemem_rgns.size; }/*
@@ -125,6 +125,8 @@ int is_crashkernel_mem_reserved(void)*/ static int crash_get_memory_ranges (void ) { +int i; +/* * First read all memory regions that can be considered as * system memory including the crash area.
@@ -132,16 +134,19 @@ static int crash_get_memory_ranges(void)if (!usablemem_rgns.size)kexec_iomem_for_each_line (NULL , iomem_range_callback,NULL ); -/* allow only a single region for crash dump kernel */ -if (usablemem_rgns.size !=1 ) +/* allow one or two regions for crash dump kernel */ +if (!usablemem_rgns.size)return -EINVAL ; -dbgprint_mem_range ("Reserved memory range" , &crash_reserved_mem,1 ); +dbgprint_mem_range ("Reserved memory range" , + usablemem_rgns.ranges, usablemem_rgns.size); -if (mem_regions_alloc_and_exclude (&system_memory_rgns, - &crash_reserved_mem)) { -fprintf (stderr,"Cannot allocate memory for ranges\n" ); -return -ENOMEM ; +for (i =0 ; i < usablemem_rgns.size; i++) { +if (mem_regions_alloc_and_exclude (&system_memory_rgns, + &crash_reserved_mem[i])) { +fprintf (stderr,"Cannot allocate memory for ranges\n" ); +return -ENOMEM ; + } }/*
@@ -202,7 +207,8 @@ int load_crashdump_segments(struct kexec_info *info)return EFAILED ; elfcorehdr =add_buffer_phys_virt (info, buf, bufsz, bufsz,0 , - crash_reserved_mem.start, crash_reserved_mem.end, + crash_reserved_mem[usablemem_rgns.size -1 ].start, + crash_reserved_mem[usablemem_rgns.size -1 ].end,-1 ,0 ); elfcorehdr_mem.start = elfcorehdr;
@@ -220,21 +226,23 @@ int load_crashdump_segments(struct kexec_info *info)* virt_to_phys() in add_segment(). * So let's fix up those values for later use so the memory base * (arm64_mm.phys_offset) will be correctly replaced with -* crash_reserved_mem.start. +* crash_reserved_mem[usablemem_rgns.size - 1].start. */ void fixup_elf_addrs (struct mem_ehdr *ehdr) {struct mem_phdr *phdr;int i; - ehdr->e_entry += - arm64_mem.phys_offset + crash_reserved_mem.start; + ehdr->e_entry += -arm64_mem.phys_offset + + crash_reserved_mem[usablemem_rgns.size -1 ].start;for (i =0 ; i < ehdr->e_phnum; i++) { phdr = &ehdr->e_phdr[i];if (phdr->p_type !=PT_LOAD )continue ; phdr->p_paddr += - (-arm64_mem.phys_offset + crash_reserved_mem.start); + (-arm64_mem.phys_offset + + crash_reserved_mem[usablemem_rgns.size -1 ].start); } }
@@ -243,11 +251,11 @@ int get_crash_kernel_load_range(uint64_t *start, uint64_t *end)if (!usablemem_rgns.size)kexec_iomem_for_each_line (NULL , iomem_range_callback,NULL ); -if (!crash_reserved_mem.end) +if (!usablemem_rgns.size)return -1 ; - *start = crash_reserved_mem.start; - *end = crash_reserved_mem.end; + *start = crash_reserved_mem[usablemem_rgns.size -1 ].start; + *end = crash_reserved_mem[usablemem_rgns.size -1 ].end;return 0 ; }
kexec/arch/arm64/crashdump-arm64.h +4 -1
@@ -16,8 +16,11 @@#define CRASH_MAX_MEMORY_RANGES 32 +/* crash dump kernel support at most two regions, low_region and high region. */ +#define CRASH_MAX_RESERVED_RANGES 2 +extern struct memory_ranges usablemem_rgns; -extern struct memory_range crash_reserved_mem; +extern struct memory_range crash_reserved_mem[];extern struct memory_range elfcorehdr_mem;extern int load_crashdump_segments (struct kexec_info *info);
kexec/arch/arm64/kexec-arm64.c +56 -28
160 lines not on this page · raw message
Signature · 1 line
2.26.0.106.g9fadedd
Simon Horman
AppliedPATCH v5 1/1 arm64: support more than one crash kernel regions
Quoted 15 lines · Zhen Lei
From: Chen Zhou <[email protected]>
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.
Currently, there is only one crash kernel region on arm64, and pass "linux,usable-memory-range = <BASE SIZE>" property to crash dump kernel.
Now, we pass "linux,usable-memory-range = <BASE1 SIZE1 BASE2 SIZE2>" to crash dump kernel to support two crash kernel regions and load crash kernel high. Make the low memory region as the second range "BASE2 SIZE2" to keep compatibility with existing user-space and older kdump kernels.
Quoted 3 lines
Signed-off-by Chen Zhou <[email protected]>Co-developed-by Zhen Lei <[email protected]>Signed-off-by Zhen Lei <[email protected]>
Thanks, applied.