From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: catalin.marinas@arm.com, thunder.leizhen@huawei.com,
John.p.donnelly@oracle.com, kexec@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, horms@kernel.org,
chenjiahao16@huawei.com, linux-riscv@lists.infradead.org,
x86@kernel.org, bp@alien8.de
Subject: Re: [RFC PATCH 0/4] kdump: add generic functions to simplify crashkernel crashkernel in architecture
Date: Mon, 19 Jun 2023 14:09:58 +0800 [thread overview]
Message-ID: <ZI/xNm23BCNcB0+v@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20230619055951.45620-1-bhe@redhat.com>
On 06/19/23 at 01:59pm, Baoquan He wrote:
> In the current arm64, crashkernel=,high support has been finished after
> several rounds of posting and careful reviewing. The code in arm64 which
> parses crashkernel kernel parameters firstly, then reserve memory can be
> a good example for other ARCH to refer to.
>
> Whereas in x86_64, the code mixing crashkernel parameter parsing and
> memory reserving is twisted, and looks messy. Refactoring the code to
> make it more readable maintainable is necessary.
^ 'and' missed
>
> Here, try to abstract the crashkernel parameter parsing code into a
> generic function parse_crashkernel_generic(), and the crashkernel memory
> reserving code into a generic function reserve_crashkernel_generic().
> Then, in ARCH which crashkernel=,high support is needed, a simple
> arch_reserve_crashkernel() can be added to call above two generic
> functions. This can remove the duplicated implmentation code in each
> ARCH, like arm64, x86_64.
>
> I only change the arm64 and x86_64 implementation to make use of the
> generic functions to simplify code. Risc-v can be done very easily refer
> to the steps in arm64 and x86_64. I leave this to Jiahao or other risc-v
> developer since Jiahao have posted a patchset to add crashkernel=,high
> support to risc-v.
>
> This patchset is based on the latest linus's tree, and on top of below
> patch:
>
> arm64: kdump: simplify the reservation behaviour of crashkernel=,high
> https://git.kernel.org/arm64/c/6c4dcaddbd36
>
>
> Baoquan He (4):
> kdump: rename parse_crashkernel() to parse_crashkernel_common()
> kdump: add generic functions to parse crashkernel and do reservation
> arm64: kdump: use generic interfaces to simplify crashkernel
> reservation code
> x86: kdump: use generic interfaces to simplify crashkernel reservation
> code
>
> arch/arm/kernel/setup.c | 4 +-
> arch/arm64/Kconfig | 3 +
> arch/arm64/include/asm/kexec.h | 8 ++
> arch/arm64/mm/init.c | 141 ++----------------------
> arch/ia64/kernel/setup.c | 4 +-
> arch/loongarch/kernel/setup.c | 3 +-
> arch/mips/cavium-octeon/setup.c | 2 +-
> arch/mips/kernel/setup.c | 4 +-
> arch/powerpc/kernel/fadump.c | 5 +-
> arch/powerpc/kexec/core.c | 4 +-
> arch/powerpc/mm/nohash/kaslr_booke.c | 4 +-
> arch/riscv/mm/init.c | 5 +-
> arch/s390/kernel/setup.c | 4 +-
> arch/sh/kernel/machine_kexec.c | 5 +-
> arch/x86/Kconfig | 3 +
> arch/x86/include/asm/kexec.h | 32 ++++++
> arch/x86/kernel/setup.c | 141 +++---------------------
> include/linux/crash_core.h | 33 +++++-
> kernel/crash_core.c | 158 +++++++++++++++++++++++++--
> 19 files changed, 274 insertions(+), 289 deletions(-)
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-06-19 6:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 5:59 [RFC PATCH 0/4] kdump: add generic functions to simplify crashkernel crashkernel in architecture Baoquan He
2023-06-19 5:59 ` [RFC PATCH 1/4] kdump: rename parse_crashkernel() to parse_crashkernel_common() Baoquan He
2023-06-19 5:59 ` [RFC PATCH 2/4] kdump: add generic functions to parse crashkernel and do reservation Baoquan He
2023-06-19 5:59 ` [RFC PATCH 3/4] arm64: kdump: use generic interfaces to simplify crashkernel reservation code Baoquan He
2023-06-19 5:59 ` [RFC PATCH 4/4] x86: " Baoquan He
2023-06-19 6:09 ` Baoquan He [this message]
2023-07-08 2:15 ` [RFC PATCH 0/4] kdump: add generic functions to simplify crashkernel crashkernel in architecture Dave Young
2023-07-10 17:20 ` Philipp Rudo
2023-08-27 10:43 ` Baoquan He
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=ZI/xNm23BCNcB0+v@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=John.p.donnelly@oracle.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenjiahao16@huawei.com \
--cc=horms@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=thunder.leizhen@huawei.com \
--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