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:54 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$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=alex@ghiti$(echo .)fr \
--cc=aou@eecs$(echo .)berkeley.edu \
--cc=ardb@kernel$(echo .)org \
--cc=bhe@redhat$(echo .)com \
--cc=bp@alien8$(echo .)de \
--cc=cfsworks@gmail$(echo .)com \
--cc=chenhuacai@kernel$(echo .)org \
--cc=chenjiahao16@huawei$(echo .)com \
--cc=chleroy@kernel$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=coxu@redhat$(echo .)com \
--cc=dapeng1.mi@linux$(echo .)intel.com \
--cc=dave.hansen@linux$(echo .)intel.com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=dyoung@redhat$(echo .)com \
--cc=eajames@linux$(echo .)ibm.com \
--cc=elver@google$(echo .)com \
--cc=feng.tang@linux$(echo .)alibaba.com \
--cc=fuqiang.wang@easystack$(echo .)cn \
--cc=guoren@kernel$(echo .)org \
--cc=hbathini@linux$(echo .)ibm.com \
--cc=hpa@zytor$(echo .)com \
--cc=james.morse@arm$(echo .)com \
--cc=jbohac@suse$(echo .)cz \
--cc=junhui.liu@pigmoral$(echo .)tech \
--cc=kees@kernel$(echo .)org \
--cc=kernel@xen0n$(echo .)name \
--cc=kevin.brodsky@arm$(echo .)com \
--cc=kexec@lists$(echo .)infradead.org \
--cc=leitao@debian$(echo .)org \
--cc=liaoyuanhong@vivo$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=lirongqing@baidu$(echo .)com \
--cc=lizhengyu3@huawei$(echo .)com \
--cc=loongarch@lists$(echo .)linux.dev \
--cc=maddy@linux$(echo .)ibm.com \
--cc=mingo@redhat$(echo .)com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=npiggin@gmail$(echo .)com \
--cc=osandov@fb$(echo .)com \
--cc=palmer@dabbelt$(echo .)com \
--cc=paulmck@kernel$(echo .)org \
--cc=pawan.kumar.gupta@linux$(echo .)intel.com \
--cc=peterz@infradead$(echo .)org \
--cc=pjw@kernel$(echo .)org \
--cc=rdunlap@infradead$(echo .)org \
--cc=ritesh.list@gmail$(echo .)com \
--cc=robh@kernel$(echo .)org \
--cc=rppt@kernel$(echo .)org \
--cc=ruanjinjie@huawei$(echo .)com \
--cc=samuel.holland@sifive$(echo .)com \
--cc=saravanak@kernel$(echo .)org \
--cc=skhan@linuxfoundation$(echo .)org \
--cc=songshuaishuai@tinylab$(echo .)org \
--cc=sourabhjain@linux$(echo .)ibm.com \
--cc=takahiro.akashi@linaro$(echo .)org \
--cc=tangyouling@kylinos$(echo .)cn \
--cc=tglx@kernel$(echo .)org \
--cc=vgoyal@redhat$(echo .)com \
--cc=vishal.moola@gmail$(echo .)com \
--cc=will@kernel$(echo .)org \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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