| Message ID | 20190403030546.23718-1-chenzhou10@huawei.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | support reserving crashkernel above 4G on arm64 kdump | expand |
Hi Chen, Thanks for the patchset. Before I review the patches in detail, I have a couple of generic queries. Please see them in-line: On 04/03/2019 11:05 AM, Chen Zhou wrote: > 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 > > 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/kernel/setup.c | 3 + > arch/arm64/mm/init.c | 108 ++++++++++++++++++++---- > include/linux/memblock.h | 1 + > mm/memblock.c | 40 +++++++++ > 5 files changed, 139 insertions(+), 17 deletions(-) I am wondering about the use-case for the same. I remember normally fedora-based arm64 systems can do well with a maximum crashkernel size of <=512MB reserved below the 4G boundary. So, do you mean that for your use-case (may be a huawei board based setup?), you need: - more than 512MB of crashkernel size, or - you want to split the crashkernel reservation across the 4GB boundary irrespective of the crashkernel size value. Thanks, Bhupesh
Hi Bhupesh, On 2019/4/9 13:20, Bhupesh Sharma wrote: > Hi Chen, > > Thanks for the patchset. > > Before I review the patches in detail, I have a couple of generic queries. Please see them in-line: > > On 04/03/2019 11:05 AM, Chen Zhou wrote: >> 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 >> >> 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/kernel/setup.c | 3 + >> arch/arm64/mm/init.c | 108 ++++++++++++++++++++---- >> include/linux/memblock.h | 1 + >> mm/memblock.c | 40 +++++++++ >> 5 files changed, 139 insertions(+), 17 deletions(-) > > I am wondering about the use-case for the same. I remember normally fedora-based arm64 systems can do well with a maximum crashkernel size of <=512MB reserved below the 4G boundary. > > So, do you mean that for your use-case (may be a huawei board based setup?), you need: > > - more than 512MB of crashkernel size, or > - you want to split the crashkernel reservation across the 4GB boundary irrespective of the crashkernel size value. > > Thanks, > Bhupesh > > > . > I do this based on below reasons. 1. ARM64 kdump support crashkernel=Y[@X], but now it seems unusable if X is specified above 4GB. 2. There are some cases we couldn't reserve 512MB crashkernel below 4G successfully if there is no continous 512MB system RAM below 4GB. In this case, we need to reserve crashkernel above 4GB. 3. As the memory increases, the bitmap_size in makedumpfile may also increases, we need more memory in kdump capture kernel for kernel dump. Thanks, Chen Zhou