From: Baoquan He <bhe@redhat•com>
To: Jinjie Ruan <ruanjinjie@huawei•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, robh@kernel•org,
saravanak@kernel•org, 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, fvdl@google•com,
rppt@kernel•org, ardb@kernel•org, leitao@debian•org,
sourabhjain@linux•ibm.com, jbohac@suse•cz, cfsworks@gmail•com,
osandov@fb•com, tangyouling@kylinos•cn, ritesh.list@gmail•com,
hbathini@linux•ibm.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,
fuqiang.wang@easystack•cn, 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,
devicetree@vger•kernel.org, kexec@lists•infradead.org
Subject: Re: [PATCH v8 0/5] arm64/riscv: Add support for crashkernel CMA reservation
Date: Tue, 10 Mar 2026 10:12:45 +0800 [thread overview]
Message-ID: <aa9-HYdKT8MhAjhi@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20260302035315.3892241-1-ruanjinjie@huawei.com>
On 03/02/26 at 11:53am, Jinjie Ruan wrote:
> The crash memory allocation, and the exclude of crashk_res, crashk_low_res
> and crashk_cma memory are almost identical across different architectures,
> This patch set handle them in crash core in a general way, which eliminate
> a lot of duplication code.
>
> And add support for crashkernel CMA reservation for arm64 and riscv.
>
> Rebased on v7.0-rc1.
>
> Basic second kernel boot test were performed on QEMU platforms for x86,
> ARM64, and RISC-V architectures with the following parameters:
>
> "cma=256M crashkernel=256M crashkernel=64M,cma"
The whole series looks good to me, thanks.
Acked-by: Baoquan He <bhe@redhat•com>
next prev parent reply other threads:[~2026-03-10 2:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 3:53 [PATCH v8 0/5] arm64/riscv: Add support for crashkernel CMA reservation Jinjie Ruan
2026-03-02 3:53 ` [PATCH v8 1/5] powerpc/crash: sort crash memory ranges before preparing elfcorehdr Jinjie Ruan
2026-03-02 3:53 ` [PATCH v8 2/5] crash: Exclude crash kernel memory in crash core Jinjie Ruan
2026-03-02 5:53 ` Sourabh Jain
2026-03-23 9:12 ` Jinjie Ruan
2026-03-02 3:53 ` [PATCH v8 3/5] crash: Use crash_exclude_core_ranges() on powerpc Jinjie Ruan
2026-03-02 5:59 ` Sourabh Jain
2026-03-02 3:53 ` [PATCH v8 4/5] arm64: kexec: Add support for crashkernel CMA reservation Jinjie Ruan
2026-03-13 21:56 ` Rob Herring (Arm)
2026-03-02 3:53 ` [PATCH v8 5/5] riscv: " Jinjie Ruan
2026-03-10 1:34 ` [PATCH v8 0/5] arm64/riscv: " Jinjie Ruan
2026-03-10 2:12 ` Baoquan He [this message]
2026-03-23 1:44 ` Jinjie Ruan
2026-03-23 1:58 ` Andrew Morton
2026-03-23 2:15 ` 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=aa9-HYdKT8MhAjhi@MiWiFi-R3L-srv \
--to=bhe@redhat$(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=bp@alien8$(echo .)de \
--cc=brgerst@gmail$(echo .)com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=cfsworks@gmail$(echo .)com \
--cc=chenhuacai@kernel$(echo .)org \
--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=fuqiang.wang@easystack$(echo .)cn \
--cc=fvdl@google$(echo .)com \
--cc=hbathini@linux$(echo .)ibm.com \
--cc=hpa@zytor$(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=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=pjw@kernel$(echo .)org \
--cc=pmladek@suse$(echo .)com \
--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=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