From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>,
corbet@lwn.net, skhan@linuxfoundation.org,
catalin.marinas@arm.com, will@kernel.org, chenhuacai@kernel.org,
kernel@xen0n.name, maddy@linux.ibm.com, mpe@ellerman.id.au,
npiggin@gmail.com, chleroy@kernel.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com, robh@kernel.org,
saravanak@kernel.org, akpm@linux-foundation.org, bhe@redhat.com,
vgoyal@redhat.com, dyoung@redhat.com, pmladek@suse.com,
rdunlap@infradead.org, dapeng1.mi@linux.intel.com,
kees@kernel.org, paulmck@kernel.org, lirongqing@baidu.com,
arnd@arndb.de, rppt@kernel.org, ardb@kernel.org,
leitao@debian.org, jbohac@suse.cz, cfsworks@gmail.com,
ryan.roberts@arm.com, tangyouling@kylinos.cn,
ritesh.list@gmail.com, hbathini@linux.ibm.com,
eajames@linux.ibm.com, songshuaishuai@tinylab.org,
samuel.holland@sifive.com, kevin.brodsky@arm.com,
vishal.moola@gmail.com, junhui.liu@pigmoral.tech,
coxu@redhat.com, liaoyuanhong@vivo.com, brgerst@gmail.com,
fuqiang.wang@easystack.cn, x86@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org,
devicetree@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH v7 3/5] crash: Use crash_exclude_core_ranges() on powerpc
Date: Fri, 27 Feb 2026 20:13:56 +0530 [thread overview]
Message-ID: <19cf18b5-362d-4ff2-8b85-e2e72809250c@linux.ibm.com> (raw)
In-Reply-To: <20260226130437.1867658-4-ruanjinjie@huawei.com>
On 26/02/26 18:34, Jinjie Ruan wrote:
> The crash memory exclude of crashk_res and crashk_cma memory on powerpc
> are almost identical to the generic crash_exclude_core_ranges().
>
> By introducing the architecture-specific arch_crash_exclude_mem_range()
> function with a default implementation of crash_exclude_mem_range(),
> and using crash_exclude_mem_range_guarded as powerpc's separate
> implementation, the generic crash_exclude_core_ranges() helper function
> can be reused.
>
> Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> ---
> arch/powerpc/kexec/ranges.c | 16 ++++------------
> include/linux/crash_core.h | 4 ++++
> kernel/crash_core.c | 19 +++++++++++++------
> 3 files changed, 21 insertions(+), 18 deletions(-)
>
> diff --git a/arch/powerpc/kexec/ranges.c b/arch/powerpc/kexec/ranges.c
> index 6c58bcc3e130..e5fea23b191b 100644
> --- a/arch/powerpc/kexec/ranges.c
> +++ b/arch/powerpc/kexec/ranges.c
> @@ -553,9 +553,9 @@ int get_usable_memory_ranges(struct crash_mem **mem_ranges)
> #endif /* CONFIG_KEXEC_FILE */
>
> #ifdef CONFIG_CRASH_DUMP
> -int crash_exclude_mem_range_guarded(struct crash_mem **mem_ranges,
> - unsigned long long mstart,
> - unsigned long long mend)
> +int arch_crash_exclude_mem_range(struct crash_mem **mem_ranges,
> + unsigned long long mstart,
> + unsigned long long mend)
> {
> struct crash_mem *tmem = *mem_ranges;
update_crash_elfcorehdr() in arch/powerpc/kexec/crash.c still calls
crash_exclude_mem_range_guarded(), causing a build failure. ld:
arch/powerpc/kexec/crash.o: in function `update_crash_elfcorehdr':
/root/linux/arch/powerpc/kexec/crash.c:454: undefined reference to
`crash_exclude_mem_range_guarded' To fix this: diff --git
a/arch/powerpc/kexec/crash.c b/arch/powerpc/kexec/crash.c index
898742a5205c..e59e909c369d 100644 --- a/arch/powerpc/kexec/crash.c +++
b/arch/powerpc/kexec/crash.c @@ -451,7 +451,7 @@ static void
update_crash_elfcorehdr(struct kimage *image, struct memory_notify *
base_addr = PFN_PHYS(mn->start_pfn); size = mn->nr_pages * PAGE_SIZE;
end = base_addr + size - 1; - ret =
crash_exclude_mem_range_guarded(&cmem, base_addr, end); + ret =
arch_crash_exclude_mem_range(&cmem, base_addr, end); if (ret) {
pr_err("Failed to remove hot-unplugged memory from crash memory
ranges\n"); goto out; With the above change included, things are working
fine on powerpc.
>
> @@ -604,18 +604,10 @@ int get_crash_memory_ranges(struct crash_mem **mem_ranges)
> sort_memory_ranges(*mem_ranges, true);
> }
>
> - /* Exclude crashkernel region */
> - ret = crash_exclude_mem_range_guarded(mem_ranges, crashk_res.start, crashk_res.end);
> + ret = crash_exclude_core_ranges(mem_ranges);
> if (ret)
> goto out;
>
> - for (i = 0; i < crashk_cma_cnt; ++i) {
> - ret = crash_exclude_mem_range_guarded(mem_ranges, crashk_cma_ranges[i].start,
> - crashk_cma_ranges[i].end);
> - if (ret)
> - goto out;
> - }
> -
> /*
> * FIXME: For now, stay in parity with kexec-tools but if RTAS/OPAL
> * regions are exported to save their context at the time of
> diff --git a/include/linux/crash_core.h b/include/linux/crash_core.h
> index 033b20204aca..dbec826dc53b 100644
> --- a/include/linux/crash_core.h
> +++ b/include/linux/crash_core.h
> @@ -68,6 +68,7 @@ extern int crash_prepare_elf64_headers(struct crash_mem *mem, int need_kernel_ma
> void **addr, unsigned long *sz);
> extern int crash_prepare_headers(int need_kernel_map, void **addr,
> unsigned long *sz, unsigned long *nr_mem_ranges);
> +extern int crash_exclude_core_ranges(struct crash_mem **cmem);
>
> struct kimage;
> struct kexec_segment;
> @@ -88,6 +89,9 @@ extern int kimage_crash_copy_vmcoreinfo(struct kimage *image);
> extern unsigned int arch_get_system_nr_ranges(void);
> extern int arch_crash_populate_cmem(struct crash_mem *cmem);
> extern int arch_crash_exclude_ranges(struct crash_mem *cmem);
> +extern int arch_crash_exclude_mem_range(struct crash_mem **mem,
> + unsigned long long mstart,
> + unsigned long long mend);
>
> #else /* !CONFIG_CRASH_DUMP*/
> struct pt_regs;
> diff --git a/kernel/crash_core.c b/kernel/crash_core.c
> index 96a96e511f5a..300d44ad5471 100644
> --- a/kernel/crash_core.c
> +++ b/kernel/crash_core.c
> @@ -287,24 +287,31 @@ unsigned int __weak arch_get_system_nr_ranges(void) { return 0; }
> int __weak arch_crash_populate_cmem(struct crash_mem *cmem) { return -1; }
> int __weak arch_crash_exclude_ranges(struct crash_mem *cmem) { return 0; }
>
> -static int crash_exclude_core_ranges(struct crash_mem *cmem)
> +int __weak arch_crash_exclude_mem_range(struct crash_mem **mem,
> + unsigned long long mstart,
> + unsigned long long mend)
> +{
> + return crash_exclude_mem_range(*mem, mstart, mend);
> +}
> +
> +int crash_exclude_core_ranges(struct crash_mem **cmem)
> {
> int ret, i;
>
> /* Exclude crashkernel region */
> - ret = crash_exclude_mem_range(cmem, crashk_res.start, crashk_res.end);
> + ret = arch_crash_exclude_mem_range(cmem, crashk_res.start, crashk_res.end);
> if (ret)
> return ret;
>
> if (crashk_low_res.end) {
> - ret = crash_exclude_mem_range(cmem, crashk_low_res.start, crashk_low_res.end);
> + ret = arch_crash_exclude_mem_range(cmem, crashk_low_res.start, crashk_low_res.end);
> if (ret)
> return ret;
> }
>
> for (i = 0; i < crashk_cma_cnt; ++i) {
> - ret = crash_exclude_mem_range(cmem, crashk_cma_ranges[i].start,
> - crashk_cma_ranges[i].end);
> + ret = arch_crash_exclude_mem_range(cmem, crashk_cma_ranges[i].start,
> + crashk_cma_ranges[i].end);
> if (ret)
> return ret;
> }
> @@ -331,7 +338,7 @@ int crash_prepare_headers(int need_kernel_map, void **addr, unsigned long *sz,
> if (ret)
> goto out;
>
> - ret = crash_exclude_core_ranges(cmem);
> + ret = crash_exclude_core_ranges(&cmem);
> if (ret)
> goto out;
>
next prev parent reply other threads:[~2026-02-27 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 13:04 [PATCH v7 0/5] arm64/riscv: Add support for crashkernel CMA reservation Jinjie Ruan
2026-02-26 13:04 ` [PATCH v7 1/5] powerpc/crash: sort crash memory ranges before preparing elfcorehdr Jinjie Ruan
2026-02-26 13:04 ` [PATCH v7 2/5] crash: Exclude crash kernel memory in crash core Jinjie Ruan
2026-02-26 13:04 ` [PATCH v7 3/5] crash: Use crash_exclude_core_ranges() on powerpc Jinjie Ruan
2026-02-27 14:43 ` Sourabh Jain [this message]
2026-02-27 14:50 ` Sourabh Jain
2026-02-28 1:21 ` Jinjie Ruan
2026-02-28 13:07 ` Sourabh Jain
2026-02-26 13:04 ` [PATCH v7 4/5] arm64: kexec: Add support for crashkernel CMA reservation Jinjie Ruan
2026-02-26 13:04 ` [PATCH v7 5/5] riscv: " Jinjie Ruan
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=19cf18b5-362d-4ff2-8b85-e2e72809250c@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=cfsworks@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=chleroy@kernel.org \
--cc=corbet@lwn.net \
--cc=coxu@redhat.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dyoung@redhat.com \
--cc=eajames@linux.ibm.com \
--cc=fuqiang.wang@easystack.cn \
--cc=hbathini@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=jbohac@suse.cz \
--cc=junhui.liu@pigmoral.tech \
--cc=kees@kernel.org \
--cc=kernel@xen0n.name \
--cc=kevin.brodsky@arm.com \
--cc=kexec@lists.infradead.org \
--cc=leitao@debian.org \
--cc=liaoyuanhong@vivo.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lirongqing@baidu.com \
--cc=loongarch@lists.linux.dev \
--cc=maddy@linux.ibm.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paulmck@kernel.org \
--cc=pjw@kernel.org \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=ritesh.list@gmail.com \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=ryan.roberts@arm.com \
--cc=samuel.holland@sifive.com \
--cc=saravanak@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=songshuaishuai@tinylab.org \
--cc=tangyouling@kylinos.cn \
--cc=tglx@kernel.org \
--cc=vgoyal@redhat.com \
--cc=vishal.moola@gmail.com \
--cc=will@kernel.org \
--cc=x86@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