From: Jinjie Ruan <ruanjinjie@huawei.com>
To: <corbet@lwn.net>, <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>, <bhe@redhat.com>,
<vgoyal@redhat.com>, <dyoung@redhat.com>, <rdunlap@infradead.org>,
<pmladek@suse.com>, <feng.tang@linux.alibaba.com>,
<pawan.kumar.gupta@linux.intel.com>, <kees@kernel.org>,
<elver@google.com>, <arnd@arndb.de>, <lirongqing@baidu.com>,
<fvdl@google.com>, <leitao@debian.org>, <rppt@kernel.org>,
<ardb@kernel.org>, <jbohac@suse.cz>, <sourabhjain@linux.ibm.com>,
<osandov@fb.com>, <ryan.roberts@arm.com>, <cfsworks@gmail.com>,
<tangyouling@kylinos.cn>, <ritesh.list@gmail.com>,
<thuth@redhat.com>, <hbathini@linux.ibm.com>,
<eajames@linux.ibm.com>, <bjorn@rivosinc.com>,
<songshuaishuai@tinylab.org>, <kevin.brodsky@arm.com>,
<samuel.holland@sifive.com>, <vishal.moola@gmail.com>,
<junhui.liu@pigmoral.tech>, <dwmw@amazon.co.uk>,
<pbonzini@redhat.com>, <thomas.lendacky@amd.com>,
<kai.huang@intel.com>, <ubizjak@gmail.com>, <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>, <kexec@lists.infradead.org>
Cc: <ruanjinjie@huawei.com>
Subject: [PATCH v4 0/3] arm64/riscv: Add support for crashkernel CMA reservation
Date: Mon, 9 Feb 2026 17:59:28 +0800 [thread overview]
Message-ID: <20260209095931.2813152-1-ruanjinjie@huawei.com> (raw)
Exclude crash kernel memory in crash core to avoid duplication. Also move
the size calculation (and the realloc if needed) into crash core.
And add support for crashkernel CMA reservation for arm64 and riscv.
Changes in v4:
- Move the size calculation (and the realloc if needed) into the
generic crash.
Changs in v3:
- Exclude crash kernel memory in crash core as Mike suggested.
- Add acked-by.
Jinjie Ruan (3):
crash: Exclude crash kernel memory in crash core
arm64: kexec: Add support for crashkernel CMA reservation
riscv: kexec: Add support for crashkernel CMA reservation
.../admin-guide/kernel-parameters.txt | 16 +--
arch/arm64/kernel/machine_kexec_file.c | 47 +-------
arch/arm64/mm/init.c | 5 +-
arch/loongarch/kernel/machine_kexec_file.c | 45 +------
arch/powerpc/include/asm/kexec.h | 13 ++
arch/powerpc/kexec/crash.c | 52 ++++----
arch/powerpc/kexec/file_load_64.c | 17 +--
arch/powerpc/kexec/ranges.c | 18 +--
arch/riscv/include/asm/kexec.h | 10 ++
arch/riscv/kernel/machine_kexec_file.c | 39 +++---
arch/riscv/mm/init.c | 5 +-
arch/x86/include/asm/kexec.h | 10 ++
arch/x86/kernel/crash.c | 104 ++--------------
include/linux/crash_core.h | 114 +++++++++++++++++-
kernel/crash_core.c | 71 +++++++++--
15 files changed, 290 insertions(+), 276 deletions(-)
--
2.34.1
next reply other threads:[~2026-02-09 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 9:59 Jinjie Ruan [this message]
2026-02-09 9:59 ` [PATCH v4 1/3] crash: Exclude crash kernel memory in crash core Jinjie Ruan
2026-02-10 12:30 ` Sourabh Jain
2026-02-12 3:28 ` Jinjie Ruan
2026-02-12 6:11 ` Sourabh Jain
2026-02-09 9:59 ` [PATCH v4 2/3] arm64: kexec: Add support for crashkernel CMA reservation Jinjie Ruan
2026-02-09 9:59 ` [PATCH v4 3/3] 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=20260209095931.2813152-1-ruanjinjie@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=bjorn@rivosinc.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=dave.hansen@linux.intel.com \
--cc=dwmw@amazon.co.uk \
--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=fvdl@google.com \
--cc=hbathini@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=jbohac@suse.cz \
--cc=junhui.liu@pigmoral.tech \
--cc=kai.huang@intel.com \
--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=osandov@fb.com \
--cc=palmer@dabbelt.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--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=songshuaishuai@tinylab.org \
--cc=sourabhjain@linux.ibm.com \
--cc=tangyouling@kylinos.cn \
--cc=tglx@kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=thuth@redhat.com \
--cc=ubizjak@gmail.com \
--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