From: Catalin Marinas <catalin.marinas@arm.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: corbet@lwn.net, skhan@linuxfoundation.org, 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, rdunlap@infradead.org,
peterz@infradead.org, pawan.kumar.gupta@linux.intel.com,
feng.tang@linux.alibaba.com, dapeng1.mi@linux.intel.com,
kees@kernel.org, elver@google.com, paulmck@kernel.org,
lirongqing@baidu.com, rppt@kernel.org, ardb@kernel.org,
leitao@debian.org, osandov@fb.com, cfsworks@gmail.com,
tangyouling@kylinos.cn, sourabhjain@linux.ibm.com,
ritesh.list@gmail.com, eajames@linux.ibm.com,
songshuaishuai@tinylab.org, kevin.brodsky@arm.com,
samuel.holland@sifive.com, vishal.moola@gmail.com,
junhui.liu@pigmoral.tech, coxu@redhat.com, liaoyuanhong@vivo.com,
jbohac@suse.cz, fuqiang.wang@easystack.cn, guoren@kernel.org,
chenjiahao16@huawei.com, hbathini@linux.ibm.com,
james.morse@arm.com, takahiro.akashi@linaro.org,
lizhengyu3@huawei.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,
devicetree@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH v10 4/8] crash: Exclude crash kernel memory in crash core
Date: Thu, 26 Mar 2026 10:53:16 +0000 [thread overview]
Message-ID: <acUQHCETMXaEtdK5@arm.com> (raw)
In-Reply-To: <20260325025904.2811960-5-ruanjinjie@huawei.com>
On Wed, Mar 25, 2026 at 10:59:00AM +0800, Jinjie Ruan wrote:
> The crash memory alloc, and the exclude of crashk_res, crashk_low_res
> and crashk_cma memory are almost identical across different architectures,
> handling them in the crash core would eliminate a lot of duplication, so
> do them in the common code.
>
> To achieve the above goal, three architecture-specific functions are
> introduced:
>
> - arch_get_system_nr_ranges(). Pre-counts the max number of memory ranges.
>
> - arch_crash_populate_cmem(). Collects the memory ranges and fills them
> into cmem.
>
> - arch_crash_exclude_ranges(). Architecture's additional crash memory
> ranges exclusion, defaulting to empty.
>
> Reviewed-by: Sourabh Jain <sourabhjain@linux.ibm.com>
> Acked-by: Baoquan He <bhe@redhat.com>
> Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
For arm64:
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2026-03-26 10:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 2:58 [PATCH v10 0/8] arm64/riscv: Add support for crashkernel CMA reservation Jinjie Ruan
2026-03-25 2:58 ` [PATCH v10 1/8] riscv: kexec_file: Fix crashk_low_res not exclude bug Jinjie Ruan
2026-03-25 2:58 ` [PATCH v10 2/8] powerpc/crash: Fix possible memory leak in update_crash_elfcorehdr() Jinjie Ruan
2026-03-25 2:58 ` [PATCH v10 3/8] powerpc/crash: sort crash memory ranges before preparing elfcorehdr Jinjie Ruan
2026-03-25 2:59 ` [PATCH v10 4/8] crash: Exclude crash kernel memory in crash core Jinjie Ruan
2026-03-26 10:53 ` Catalin Marinas [this message]
2026-03-25 2:59 ` [PATCH v10 5/8] crash: Use crash_exclude_core_ranges() on powerpc Jinjie Ruan
2026-03-25 2:59 ` [PATCH v10 6/8] arm64: kexec: Add support for crashkernel CMA reservation Jinjie Ruan
2026-03-26 10:54 ` Catalin Marinas
2026-03-25 2:59 ` [PATCH v10 7/8] riscv: " Jinjie Ruan
2026-03-25 2:59 ` [PATCH v10 8/8] crash: Fix race condition between crash kernel loading and memory hotplug Jinjie Ruan
2026-03-26 4:00 ` [PATCH v10 0/8] arm64/riscv: Add support for crashkernel CMA reservation Andrew Morton
2026-03-26 13:09 ` 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=acUQHCETMXaEtdK5@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=cfsworks@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=chenjiahao16@huawei.com \
--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=elver@google.com \
--cc=feng.tang@linux.alibaba.com \
--cc=fuqiang.wang@easystack.cn \
--cc=guoren@kernel.org \
--cc=hbathini@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.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=lizhengyu3@huawei.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=osandov@fb.com \
--cc=palmer@dabbelt.com \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=rdunlap@infradead.org \
--cc=ritesh.list@gmail.com \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=samuel.holland@sifive.com \
--cc=saravanak@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=songshuaishuai@tinylab.org \
--cc=sourabhjain@linux.ibm.com \
--cc=takahiro.akashi@linaro.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