Re: [PATCH v16 00/11] support reserving crashkernel above 4G on arm64 kdump
On Fri, Dec 10, 2021 at 01:53:59PM -0600, john.p.donne...@oracle.com wrote: > On 12/8/21 11:13 AM, Catalin Marinas wrote: > > On Tue, Nov 23, 2021 at 08:46:35PM +0800, Zhen Lei wrote: > > > Chen Zhou (10): > > >x86: kdump: replace the hard-coded alignment with macro CRASH_ALIGN > > >x86: kdump: make the lower bound of crash kernel reservation > > > consistent > > >x86: kdump: use macro CRASH_ADDR_LOW_MAX in functions > > > reserve_crashkernel() > > >x86: kdump: move xen_pv_domain() check and insert_resource() to > > > setup_arch() > > >x86: kdump: move reserve_crashkernel[_low]() into crash_core.c > > >arm64: kdump: introduce some macros for crash kernel reservation > > >arm64: kdump: reimplement crashkernel=X > > >x86, arm64: Add ARCH_WANT_RESERVE_CRASH_KERNEL config > > >of: fdt: Add memory for devices by DT property > > > "linux,usable-memory-range" > > >kdump: update Documentation about crashkernel > > > > > > Zhen Lei (1): > > >of: fdt: Aggregate the processing of "linux,usable-memory-range" > > > > Apart from a minor comment I made on patch 8 and some comments from Rob > > that need addressing, the rest looks fine to me. > > > > Ingo stated in the past that he's happy to ack the x86 changes as long > > as there's no functional change (and that's the case AFAICT). Ingo, does > > your conditional ack still stand? > > > > In terms of merging, I'm happy to take it all through the arm64 tree > > with acks from the x86 maintainers. Alternatively, with the change I > > mentioned for patch 8, the first 5 patches could be queued via the tip > > tree on a stable branch and I can base the rest of the arm64 on top. > > > > Thomas, Ingo, Peter, any preference? > > > > Thanks. > > If you notice the trend over the past year , some of additional review > requests are because the submitter had to rebase to the next version. Normally the reviews stand even if the series is rebased. You only drop them if there were non-trivial changes to the patches, not just because of a rebase. Ingo acked the x86 changes in the past but there were some functional changes to the minimum alignment, so the series had to be reworked and the ack not applied. https://lore.kernel.org/r/20200806133627.gb2077...@gmail.com > Can we get this acked and placed in a build so others can test and start > using it ? If Ingo's conditional ack (no functional changes, just a move) still stands over the five x86 patches now, I'm happy to queue them all via the arm64 tree. The latest series here: https://lore.kernel.org/r/20211210065533.2023-1-thunder.leiz...@huawei.com -- Catalin ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH v16 00/11] support reserving crashkernel above 4G on arm64 kdump
On 12/8/21 11:13 AM, Catalin Marinas wrote: On Tue, Nov 23, 2021 at 08:46:35PM +0800, Zhen Lei wrote: Chen Zhou (10): x86: kdump: replace the hard-coded alignment with macro CRASH_ALIGN x86: kdump: make the lower bound of crash kernel reservation consistent x86: kdump: use macro CRASH_ADDR_LOW_MAX in functions reserve_crashkernel() x86: kdump: move xen_pv_domain() check and insert_resource() to setup_arch() x86: kdump: move reserve_crashkernel[_low]() into crash_core.c arm64: kdump: introduce some macros for crash kernel reservation arm64: kdump: reimplement crashkernel=X x86, arm64: Add ARCH_WANT_RESERVE_CRASH_KERNEL config of: fdt: Add memory for devices by DT property "linux,usable-memory-range" kdump: update Documentation about crashkernel Zhen Lei (1): of: fdt: Aggregate the processing of "linux,usable-memory-range" Apart from a minor comment I made on patch 8 and some comments from Rob that need addressing, the rest looks fine to me. Ingo stated in the past that he's happy to ack the x86 changes as long as there's no functional change (and that's the case AFAICT). Ingo, does your conditional ack still stand? In terms of merging, I'm happy to take it all through the arm64 tree with acks from the x86 maintainers. Alternatively, with the change I mentioned for patch 8, the first 5 patches could be queued via the tip tree on a stable branch and I can base the rest of the arm64 on top. Thomas, Ingo, Peter, any preference? Thanks. Hi, If you notice the trend over the past year , some of additional review requests are because the submitter had to rebase to the next version. Can we get this acked and placed in a build so others can test and start using it ? Thank you, JD ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH v16 00/11] support reserving crashkernel above 4G on arm64 kdump
On Tue, Nov 23, 2021 at 08:46:35PM +0800, Zhen Lei wrote: > Chen Zhou (10): > x86: kdump: replace the hard-coded alignment with macro CRASH_ALIGN > x86: kdump: make the lower bound of crash kernel reservation > consistent > x86: kdump: use macro CRASH_ADDR_LOW_MAX in functions > reserve_crashkernel() > x86: kdump: move xen_pv_domain() check and insert_resource() to > setup_arch() > x86: kdump: move reserve_crashkernel[_low]() into crash_core.c > arm64: kdump: introduce some macros for crash kernel reservation > arm64: kdump: reimplement crashkernel=X > x86, arm64: Add ARCH_WANT_RESERVE_CRASH_KERNEL config > of: fdt: Add memory for devices by DT property > "linux,usable-memory-range" > kdump: update Documentation about crashkernel > > Zhen Lei (1): > of: fdt: Aggregate the processing of "linux,usable-memory-range" Apart from a minor comment I made on patch 8 and some comments from Rob that need addressing, the rest looks fine to me. Ingo stated in the past that he's happy to ack the x86 changes as long as there's no functional change (and that's the case AFAICT). Ingo, does your conditional ack still stand? In terms of merging, I'm happy to take it all through the arm64 tree with acks from the x86 maintainers. Alternatively, with the change I mentioned for patch 8, the first 5 patches could be queued via the tip tree on a stable branch and I can base the rest of the arm64 on top. Thomas, Ingo, Peter, any preference? Thanks. -- Catalin ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH v16 00/11] support reserving crashkernel above 4G on arm64 kdump
On 11/23/21 6:46 AM, Zhen Lei wrote:
There are following issues in arm64 kdump:
1. We use crashkernel=X to reserve crashkernel below 4G, which
will fail when there is no enough low memory.
2. If reserving crashkernel above 4G, in this case, crash dump
kernel will boot failure because there is no low memory available
for allocation.
To solve these issues, change the behavior of crashkernel=X.
crashkernel=X tries low allocation in DMA zone and fall back to high
allocation if it fails.
We can also use "crashkernel=X,high" to select a high region above
DMA zone, which also tries to allocate at least 256M low memory in
DMA zone automatically and "crashkernel=Y,low" can be used to allocate
specified size low memory.
When reserving crashkernel in high memory, some low memory is reserved
for crash dump kernel devices. So there may be two regions reserved for
crash dump kernel.
In order to distinct from the high region and make no effect to the use
of existing kexec-tools, rename the low region as "Crash kernel (low)",
and pass the low region by reusing DT property
"linux,usable-memory-range". We made the low memory region as the last
range of "linux,usable-memory-range" to keep compatibility with existing
user-space and older kdump kernels.
Besides, we need to modify kexec-tools:
arm64: support more than one crash kernel regions(see [1])
Another update is document about DT property 'linux,usable-memory-range':
schemas: update 'linux,usable-memory-range' node schema(see [2])
This patchset contains the following 11 patches:
0001-0004 are some x86 cleanups which prepares for making
functionsreserve_crashkernel[_low]() generic.
0005 makes functions reserve_crashkernel[_low]() generic.
0006-0008 reimplements arm64 crashkernel=X.
0009-0010 adds memory for devices by DT property linux,usable-memory-range.
0011 updates the doc.
Changes since [v15]
- Aggregate the processing of "linux,usable-memory-range" into one function.
Only patch 9-10 have been updated.
Changes since [v14]
- Recovering the requirement that the CrashKernel memory regions on X86
only requires 1 MiB alignment.
- Combine patches 5 and 6 in v14 into one. The compilation warning fixed
by patch 6 was introduced by patch 5 in v14.
- As with crashk_res, crashk_low_res is also processed by
crash_exclude_mem_range() in patch 7.
- Due to commit b261dba2fdb2 ("arm64: kdump: Remove custom linux,usable-memory-range
handling")
has removed the architecture-specific code, extend the property
"linux,usable-memory-range"
in the platform-agnostic FDT core code. See patch 9.
- Discard the x86 description update in the document, because the description
has been updated by commit b1f4c363666c ("Documentation: kdump: update kdump
guide").
- Change "arm64" to "ARM64" in Doc.
Changes since [v13]
- Rebased on top of 5.11-rc5.
- Introduce config CONFIG_ARCH_WANT_RESERVE_CRASH_KERNEL.
Since reserve_crashkernel[_low]() implementations are quite similar on
other architectures, so have CONFIG_ARCH_WANT_RESERVE_CRASH_KERNEL in
arch/Kconfig and select this by X86 and ARM64.
- Some minor cleanup.
Changes since [v12]
- Rebased on top of 5.10-rc1.
- Keep CRASH_ALIGN as 16M suggested by Dave.
- Drop patch "kdump: add threshold for the required memory".
- Add Tested-by from John.
Changes since [v11]
- Rebased on top of 5.9-rc4.
- Make the function reserve_crashkernel() of x86 generic.
Suggested by Catalin, make the function reserve_crashkernel() of x86 generic
and arm64 use the generic version to reimplement crashkernel=X.
Changes since [v10]
- Reimplement crashkernel=X suggested by Catalin, Many thanks to Catalin.
Changes since [v9]
- Patch 1 add Acked-by from Dave.
- Update patch 5 according to Dave's comments.
- Update chosen schema.
Changes since [v8]
- Reuse DT property "linux,usable-memory-range".
Suggested by Rob, reuse DT property "linux,usable-memory-range" to pass the low
memory region.
- Fix kdump broken with ZONE_DMA reintroduced.
- Update chosen schema.
Changes since [v7]
- Move x86 CRASH_ALIGN to 2M
Suggested by Dave and do some test, move x86 CRASH_ALIGN to 2M.
- Update Documentation/devicetree/bindings/chosen.txt.
Add corresponding documentation to Documentation/devicetree/bindings/chosen.txt
suggested by Arnd.
- Add Tested-by from Jhon and pk.
Changes since [v6]
- Fix build errors reported by kbuild test robot.
Changes since [v5]
- Move reserve_crashkernel_low() into kernel/crash_core.c.
- Delete crashkernel=X,high.
- Modify crashkernel=X,low.
If crashkernel=X,low is specified simultaneously, reserve spcified size low
memory for crash kdump kernel devices firstly and then reserve memory above 4G.
In addition, rename crashk_low_res as "Crash kernel (low)" for arm64, and then
pass to crash dump kernel by DT property "linux,low-memory-range".
- Update Documentation/admin-guide/kdump/kdump.rst.
Changes since [v4]
- Reimplement memblock_cap_memory_ranges for multiple ranges by Mike.
Changes since [v3]
- Add
Re: [PATCH v16 00/11] support reserving crashkernel above 4G on arm64 kdump
Hi Lei,
On 11/23/21 at 08:46pm, Zhen Lei wrote:
> There are following issues in arm64 kdump:
> 1. We use crashkernel=X to reserve crashkernel below 4G, which
> will fail when there is no enough low memory.
> 2. If reserving crashkernel above 4G, in this case, crash dump
> kernel will boot failure because there is no low memory available
> for allocation.
>
> To solve these issues, change the behavior of crashkernel=X.
> crashkernel=X tries low allocation in DMA zone and fall back to high
> allocation if it fails.
Thanks for this round of posting, I will review the patch series this
week.
Thanks
Baoquan
>
> We can also use "crashkernel=X,high" to select a high region above
> DMA zone, which also tries to allocate at least 256M low memory in
> DMA zone automatically and "crashkernel=Y,low" can be used to allocate
> specified size low memory.
>
> When reserving crashkernel in high memory, some low memory is reserved
> for crash dump kernel devices. So there may be two regions reserved for
> crash dump kernel.
> In order to distinct from the high region and make no effect to the use
> of existing kexec-tools, rename the low region as "Crash kernel (low)",
> and pass the low region by reusing DT property
> "linux,usable-memory-range". We made the low memory region as the last
> range of "linux,usable-memory-range" to keep compatibility with existing
> user-space and older kdump kernels.
>
> Besides, we need to modify kexec-tools:
> arm64: support more than one crash kernel regions(see [1])
>
> Another update is document about DT property 'linux,usable-memory-range':
> schemas: update 'linux,usable-memory-range' node schema(see [2])
>
> This patchset contains the following 11 patches:
>
> 0001-0004 are some x86 cleanups which prepares for making
> functionsreserve_crashkernel[_low]() generic.
> 0005 makes functions reserve_crashkernel[_low]() generic.
> 0006-0008 reimplements arm64 crashkernel=X.
> 0009-0010 adds memory for devices by DT property linux,usable-memory-range.
> 0011 updates the doc.
>
> Changes since [v15]
> - Aggregate the processing of "linux,usable-memory-range" into one function.
>Only patch 9-10 have been updated.
>
> Changes since [v14]
> - Recovering the requirement that the CrashKernel memory regions on X86
> only requires 1 MiB alignment.
> - Combine patches 5 and 6 in v14 into one. The compilation warning fixed
> by patch 6 was introduced by patch 5 in v14.
> - As with crashk_res, crashk_low_res is also processed by
> crash_exclude_mem_range() in patch 7.
> - Due to commit b261dba2fdb2 ("arm64: kdump: Remove custom
> linux,usable-memory-range handling")
> has removed the architecture-specific code, extend the property
> "linux,usable-memory-range"
> in the platform-agnostic FDT core code. See patch 9.
> - Discard the x86 description update in the document, because the description
> has been updated by commit b1f4c363666c ("Documentation: kdump: update
> kdump guide").
> - Change "arm64" to "ARM64" in Doc.
>
>
> Changes since [v13]
> - Rebased on top of 5.11-rc5.
> - Introduce config CONFIG_ARCH_WANT_RESERVE_CRASH_KERNEL.
> Since reserve_crashkernel[_low]() implementations are quite similar on
> other architectures, so have CONFIG_ARCH_WANT_RESERVE_CRASH_KERNEL in
> arch/Kconfig and select this by X86 and ARM64.
> - Some minor cleanup.
>
> Changes since [v12]
> - Rebased on top of 5.10-rc1.
> - Keep CRASH_ALIGN as 16M suggested by Dave.
> - Drop patch "kdump: add threshold for the required memory".
> - Add Tested-by from John.
>
> Changes since [v11]
> - Rebased on top of 5.9-rc4.
> - Make the function reserve_crashkernel() of x86 generic.
> Suggested by Catalin, make the function reserve_crashkernel() of x86 generic
> and arm64 use the generic version to reimplement crashkernel=X.
>
> Changes since [v10]
> - Reimplement crashkernel=X suggested by Catalin, Many thanks to Catalin.
>
> Changes since [v9]
> - Patch 1 add Acked-by from Dave.
> - Update patch 5 according to Dave's comments.
> - Update chosen schema.
>
> Changes since [v8]
> - Reuse DT property "linux,usable-memory-range".
> Suggested by Rob, reuse DT property "linux,usable-memory-range" to pass the
> low
> memory region.
> - Fix kdump broken with ZONE_DMA reintroduced.
> - Update chosen schema.
>
> Changes since [v7]
> - Move x86 CRASH_ALIGN to 2M
> Suggested by Dave and do some test, move x86 CRASH_ALIGN to 2M.
> - Update Documentation/devicetree/bindings/chosen.txt.
> Add corresponding documentation to
> Documentation/devicetree/bindings/chosen.txt
> suggested by Arnd.
> - Add Tested-by from Jhon and pk.
>
> Changes since [v6]
> - Fix build errors reported by kbuild test robot.
>
> Changes since [v5]
> - Move reserve_crashkernel_low() into kernel/crash_core.c.
> - Delete crashkernel=X,high.
> - Modify crashkernel=X,low.
> If crashkernel=X,low is specified simultaneously, reserve spcified size low
> memory for crash kdump kernel devices firstly and then reserve memory above
> 4G.
Re: [PATCH v16 00/11] support reserving crashkernel above 4G on arm64 kdump
For the series: Tested-by: Dave Kleikamp ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
