From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Baoquan He <bhe@redhat.com>
Cc: <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>, <akpm@linux-foundation.org>, <vgoyal@redhat.com>,
<dyoung@redhat.com>, <rdunlap@infradead.org>, <pmladek@suse.com>,
<dapeng1.mi@linux.intel.com>, <kees@kernel.org>,
<paulmck@kernel.org>, <lirongqing@baidu.com>, <arnd@arndb.de>,
<ardb@kernel.org>, <leitao@debian.org>, <rppt@kernel.org>,
<cfsworks@gmail.com>, <ryan.roberts@arm.com>,
<sourabhjain@linux.ibm.com>, <tangyouling@kylinos.cn>,
<eajames@linux.ibm.com>, <hbathini@linux.ibm.com>,
<ritesh.list@gmail.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>,
<fuqiang.wang@easystack.cn>, <jbohac@suse.cz>,
<brgerst@gmail.com>, <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>, <kexec@lists.infradead.org>
Subject: Re: [PATCH v6 1/5] powerpc/crash: sort crash memory ranges before preparing elfcorehdr
Date: Thu, 26 Feb 2026 17:35:14 +0800 [thread overview]
Message-ID: <15ea8a98-2b0c-dd51-b0d4-911905b194c3@huawei.com> (raw)
In-Reply-To: <aaARRZh9k_0oG3Qo@MiWiFi-R3L-srv>
On 2026/2/26 17:24, Baoquan He wrote:
> On 02/24/26 at 04:53pm, Jinjie Ruan wrote:
>> From: Sourabh Jain <sourabhjain@linux.ibm.com>
>>
>> During a memory hot-remove event, the elfcorehdr is rebuilt to exclude
>> the removed memory. While updating the crash memory ranges for this
>> operation, the crash memory ranges array can become unsorted. This
>> happens because remove_mem_range() may split a memory range into two
>> parts and append the higher-address part as a separate range at the end
>> of the array.
>>
>> So far, no issues have been observed due to the unsorted crash memory
>> ranges. However, this could lead to problems once crash memory range
>> removal is handled by generic code, as introduced in the upcoming
>> patches in this series.
>>
>> Currently, powerpc uses a platform-specific function,
>> remove_mem_range(), to exclude hot-removed memory from the crash memory
>> ranges. This function performs the same task as the generic
>> crash_exclude_mem_range() in crash_core.c. The generic helper also
>> ensures that the crash memory ranges remain sorted. So remove the
>> redundant powerpc-specific implementation and instead call
>> crash_exclude_mem_range_guarded() (which internally calls
>> crash_exclude_mem_range()) to exclude the hot-removed memory ranges.
>>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Baoquan he <bhe@redhat.com>
>> Cc: Jinjie Ruan <ruanjinjie@huawei.com>
>> Cc: Hari Bathini <hbathini@linux.ibm.com>
>> Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
>> Cc: Mahesh Salgaonkar <mahesh@linux.ibm.com>
>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>> Cc: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
>> Cc: Shivang Upadhyay <shivangu@linux.ibm.com>
>> Cc: linux-kernel@vger.kernel.org
>> Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
>> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
>
> You should add your own Signed-off-by since you sent it out.
Ack, I'll add my Signed-off-by in the next revision.
Thanks,
>
>> ---
>> arch/powerpc/include/asm/kexec_ranges.h | 4 +-
>> arch/powerpc/kexec/crash.c | 5 +-
>> arch/powerpc/kexec/ranges.c | 87 +------------------------
>> 3 files changed, 7 insertions(+), 89 deletions(-)
> ......snip...
>
>
next prev parent reply other threads:[~2026-02-26 9:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 8:53 [PATCH v6 0/5] arm64/riscv: Add support for crashkernel CMA reservation Jinjie Ruan
2026-02-24 8:53 ` [PATCH v6 1/5] powerpc/crash: sort crash memory ranges before preparing elfcorehdr Jinjie Ruan
2026-02-25 3:15 ` Ritesh Harjani
2026-02-26 9:24 ` Baoquan He
2026-02-26 9:35 ` Jinjie Ruan [this message]
2026-02-24 8:53 ` [PATCH v6 2/5] crash: Exclude crash kernel memory in crash core Jinjie Ruan
2026-02-26 9:29 ` Baoquan He
2026-02-24 8:53 ` [PATCH v6 3/5] crash: Use crash_exclude_core_ranges() on powerpc Jinjie Ruan
2026-02-24 8:53 ` [PATCH v6 4/5] arm64: kexec: Add support for crashkernel CMA reservation Jinjie Ruan
2026-02-25 15:48 ` Mike Rapoport
2026-02-26 3:24 ` Jinjie Ruan
2026-02-26 9:33 ` Baoquan He
2026-02-24 8:53 ` [PATCH v6 5/5] riscv: " Jinjie Ruan
2026-02-25 15:50 ` [PATCH v6 0/5] arm64/riscv: " 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=15ea8a98-2b0c-dd51-b0d4-911905b194c3@huawei.com \
--to=ruanjinjie@huawei.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=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=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=samuel.holland@sifive.com \
--cc=skhan@linuxfoundation.org \
--cc=songshuaishuai@tinylab.org \
--cc=sourabhjain@linux.ibm.com \
--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