From: Mike Rapoport <rppt@kernel.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: ardb@kernel.org, leitao@debian.org, corbet@lwn.net,
catalin.marinas@arm.com, will@kernel.org,
akpm@linux-foundation.org, bp@alien8.de, mingo@kernel.org,
pawan.kumar.gupta@linux.intel.com, feng.tang@linux.alibaba.com,
kees@kernel.org, elver@google.com, arnd@arndb.de,
fvdl@google.com, lirongqing@baidu.com, bhelgaas@google.com,
bhe@redhat.com, dave.hansen@linux.intel.com, cfsworks@gmail.com,
osandov@fb.com, sourabhjain@linux.ibm.com, jbohac@suse.cz,
ryan.roberts@arm.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: kexec: Add support for crashkernel CMA reservation
Date: Wed, 28 Jan 2026 10:31:51 +0200 [thread overview]
Message-ID: <aXnJd_Xghj9JLsnK@kernel.org> (raw)
In-Reply-To: <20260126081334.699147-1-ruanjinjie@huawei.com>
On Mon, Jan 26, 2026 at 04:13:34PM +0800, Jinjie Ruan wrote:
> Commit 35c18f2933c5 ("Add a new optional ",cma" suffix to the
> crashkernel= command line option") and commit ab475510e042 ("kdump:
> implement reserve_crashkernel_cma") added CMA support for kdump
> crashkernel reservation.
>
> Crash kernel memory reservation wastes production resources if too
> large, risks kdump failure if too small, and faces allocation difficulties
> on fragmented systems due to contiguous block constraints. The new
> CMA-based crashkernel reservation scheme splits the "large fixed
> reservation" into a "small fixed region + large CMA dynamic region": the
> CMA memory is available to userspace during normal operation to avoid
> waste, and is reclaimed for kdump upon crash—saving memory while
> improving reliability.
>
> So extend crashkernel CMA reservation support to arm64. The following
> changes are made to enable CMA reservation:
>
> - Parse and obtain the CMA reservation size along with other crashkernel
> parameters.
> - Call reserve_crashkernel_cma() to allocate the CMA region for kdump.
> - Include the CMA-reserved ranges for kdump kernel to use.
> - Exclude the CMA-reserved ranges from the crash kernel memory to
> prevent them from being exported through /proc/vmcore.
>
> Update kernel-parameters.txt to document CMA support for crashkernel on
> arm64 architecture.
I'm looking at this and at almost identical patch for riscv
https://lore.kernel.org/all/20260126080738.696723-1-ruanjinjie@huawei.com
and it feels wrong that we have duplicate the code that excludes cma
ranges.
CMA ranges are known to the crash_core and I don't see why we cannot
exclude them there.
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> ---
> v2:
> - Free cmem in prepare_elf_headers()
> - Add the mtivation.
> ---
> Documentation/admin-guide/kernel-parameters.txt | 2 +-
> arch/arm64/kernel/machine_kexec_file.c | 15 ++++++++++++++-
> arch/arm64/mm/init.c | 5 +++--
> 3 files changed, 18 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 1058f2a6d6a8..36bb642a7edd 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -1119,7 +1119,7 @@ Kernel parameters
> It will be ignored when crashkernel=X,high is not used
> or memory reserved is below 4G.
> crashkernel=size[KMG],cma
> - [KNL, X86, ppc] Reserve additional crash kernel memory from
> + [KNL, X86, ARM64, ppc] Reserve additional crash kernel memory from
> CMA. This reservation is usable by the first system's
> userspace memory and kernel movable allocations (memory
> balloon, zswap). Pages allocated from this memory range
> diff --git a/arch/arm64/kernel/machine_kexec_file.c b/arch/arm64/kernel/machine_kexec_file.c
> index 410060ebd86d..ef6ce9aaba80 100644
> --- a/arch/arm64/kernel/machine_kexec_file.c
> +++ b/arch/arm64/kernel/machine_kexec_file.c
> @@ -48,7 +48,7 @@ static int prepare_elf_headers(void **addr, unsigned long *sz)
> u64 i;
> phys_addr_t start, end;
>
> - nr_ranges = 2; /* for exclusion of crashkernel region */
> + nr_ranges = 2 + crashk_cma_cnt; /* for exclusion of crashkernel region */
> for_each_mem_range(i, &start, &end)
> nr_ranges++;
>
> @@ -64,6 +64,12 @@ static int prepare_elf_headers(void **addr, unsigned long *sz)
> cmem->nr_ranges++;
> }
>
> + for (i = 0; i < crashk_cma_cnt; i++) {
> + cmem->ranges[cmem->nr_ranges].start = crashk_cma_ranges[i].start;
> + cmem->ranges[cmem->nr_ranges].end = crashk_cma_ranges[i].end;
> + cmem->nr_ranges++;
> + }
> +
> /* Exclude crashkernel region */
> ret = crash_exclude_mem_range(cmem, crashk_res.start, crashk_res.end);
> if (ret)
> @@ -75,6 +81,13 @@ static int prepare_elf_headers(void **addr, unsigned long *sz)
> goto out;
> }
>
> + for (i = 0; i < crashk_cma_cnt; ++i) {
> + ret = crash_exclude_mem_range(cmem, crashk_cma_ranges[i].start,
> + crashk_cma_ranges[i].end);
> + if (ret)
> + goto out;
> + }
> +
> ret = crash_prepare_elf64_headers(cmem, true, addr, sz);
>
> out:
> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> index 524d34a0e921..28165d94af08 100644
> --- a/arch/arm64/mm/init.c
> +++ b/arch/arm64/mm/init.c
> @@ -96,8 +96,8 @@ phys_addr_t __ro_after_init arm64_dma_phys_limit;
>
> static void __init arch_reserve_crashkernel(void)
> {
> + unsigned long long crash_base, crash_size, cma_size = 0;
> unsigned long long low_size = 0;
> - unsigned long long crash_base, crash_size;
> bool high = false;
> int ret;
>
> @@ -106,11 +106,12 @@ static void __init arch_reserve_crashkernel(void)
>
> ret = parse_crashkernel(boot_command_line, memblock_phys_mem_size(),
> &crash_size, &crash_base,
> - &low_size, NULL, &high);
> + &low_size, &cma_size, &high);
> if (ret)
> return;
>
> reserve_crashkernel_generic(crash_size, crash_base, low_size, high);
> + reserve_crashkernel_cma(cma_size);
> }
>
> static phys_addr_t __init max_zone_phys(phys_addr_t zone_limit)
> --
> 2.34.1
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-01-28 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 8:13 [PATCH v2] arm64: kexec: Add support for crashkernel CMA reservation Jinjie Ruan
2026-01-27 22:45 ` Ard Biesheuvel
2026-01-28 8:31 ` Mike Rapoport [this message]
2026-01-28 9:10 ` Jinjie Ruan
2026-01-28 9:25 ` Mike Rapoport
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aXnJd_Xghj9JLsnK@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=cfsworks@gmail.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=elver@google.com \
--cc=feng.tang@linux.alibaba.com \
--cc=fvdl@google.com \
--cc=jbohac@suse.cz \
--cc=kees@kernel.org \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mingo@kernel.org \
--cc=osandov@fb.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=ruanjinjie@huawei.com \
--cc=ryan.roberts@arm.com \
--cc=sourabhjain@linux.ibm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox