From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: catalin.marinas@arm.com, will@kernel.org, horms@kernel.org,
thunder.leizhen@huawei.com, John.p.donnelly@oracle.com,
kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
Baoquan He <bhe@redhat.com>
Subject: [PATCH v6 0/2] arm64: kdump: simplify the reservation behaviour of crashkernel=,high
Date: Mon, 15 May 2023 14:02:57 +0800 [thread overview]
Message-ID: <20230515060259.830662-1-bhe@redhat.com> (raw)
In v5 patch, Catalin helped review and acked the patch. However, an
uninitialized local varilable is warned out by static checker when Will
tried to merge the patch. And Will complained the code flow in
reserve_crashkernel() is hard to follow, required to refactor. While
when I tried to do the refactory, I feel it's not easy, the existing
several cases causes that.
To make the code easier understand, I try my best to compose a document
to introduce the background, concept and implementation strategies of
crashkernel reservation. Hope it can help people to understand the code
flow a little more easily.
[PATCH v5] arm64: kdump: simplify the reservation behaviour of crashkernel=,high
https://lore.kernel.org/all/20230407022419.19412-1-bhe@redhat.com/T/#u
v5->v6:
- Fix the warning reported by static checker about "uninitialized symbol
'search_base'".
- Add a document Documentation/arm64/kdump.rst to explain how to reserve
crashkernel.
Baoquan He (2):
arm64: kdump: simplify the reservation behaviour of crashkernel=,high
Documentation: add kdump.rst to present crashkernel reservation on
arm64
Documentation/arm64/kdump.rst | 103 ++++++++++++++++++++++++++++++++++
arch/arm64/mm/init.c | 44 +++++++++++----
2 files changed, 137 insertions(+), 10 deletions(-)
create mode 100644 Documentation/arm64/kdump.rst
--
2.34.1
next reply other threads:[~2023-05-15 6:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 6:02 Baoquan He [this message]
2023-05-15 6:02 ` [PATCH v6 1/2] arm64: kdump: simplify the reservation behaviour of crashkernel=,high Baoquan He
2023-05-15 9:54 ` [PATCH v6 RESEND " Baoquan He
2023-06-06 11:53 ` Leizhen (ThunderTown)
2023-05-15 10:07 ` [PATCH v6 " Baoquan He
2023-05-15 6:02 ` [PATCH v6 2/2] Documentation: add kdump.rst to present crashkernel reservation on arm64 Baoquan He
2023-06-06 12:08 ` Leizhen (ThunderTown)
2023-06-09 19:30 ` [PATCH v6 0/2] arm64: kdump: simplify the reservation behaviour of crashkernel=,high Catalin Marinas
2023-06-11 0:35 ` Baoquan He
2023-06-11 12:15 ` Baoquan He
2023-06-11 14:31 ` Catalin Marinas
2023-06-11 23:06 ` 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=20230515060259.830662-1-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=John.p.donnelly@oracle.com \
--cc=catalin.marinas@arm.com \
--cc=horms@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder.leizhen@huawei.com \
--cc=will@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).