From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Rob Herring <robh+dt@kernel.org>,
Nick Kossifidis <mick@ics.forth.gr>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Frank Rowand <frowand.list@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/3] Add generic-support for linux,elfcorehdr and fix riscv
Date: Tue, 15 Jun 2021 20:17:24 +0200 [thread overview]
Message-ID: <cover.1623780059.git.geert+renesas@glider.be> (raw)
Hi all,
While working on v4 of "[PATCH v3] ARM: Parse kdump DT properties", I
noticed the recently (v5.13-rc1) introduced RISC-V crash kernel support
uses "linux,elfcorehdr" in a non-standard way. Instead of relying on a
"linux,elfcorehdr" property under the "/chosen" node, RISC-V uses a
reserved memory node with the "linux,elfcorehdr" compatible value.
As we may want to fix riscv before the release of v5.13, I decided not
to wait until my full v4 is ready, but fast-track generic
"linux,elfcorehdr" handling instead.
This series consists of 3 patches:
1. Generic handling of "linux,elfcorehdr", as requested by Rob in a
review comment for [1],
2. Drop the non-standard code from riscv. It can just use the generic
code instead (needs corresponding changes to WIP kexec-tools),
3. Drop the now duplicate code from arm64. This can be postponed, as
it can co-exist safely with the generic code.
This has been tested on arm32 (with a WIP successor of [1]), and
compile-tested on riscv64 and arm64.
Thanks for your comments!
[1] "[PATCH v3] ARM: Parse kdump DT properties"
https://lore.kernel.org/linux-devicetree/20210317113130.2554368-1-geert+renesas@glider.be/
Geert Uytterhoeven (3):
of: fdt: Add generic support for parsing elf core header properties
riscv: Remove non-standard linux,elfcorehdr handling
arm64: kdump: Remove custom linux,elfcorehdr parsing
Documentation/devicetree/bindings/chosen.txt | 6 ++--
arch/arm64/mm/init.c | 21 -----------
arch/riscv/mm/init.c | 20 -----------
drivers/of/fdt.c | 37 ++++++++++++++++++--
4 files changed, 37 insertions(+), 47 deletions(-)
--
2.25.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2021-06-15 18:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 18:17 Geert Uytterhoeven [this message]
2021-06-15 18:17 ` [PATCH 1/3] of: fdt: Add generic support for parsing elf core header properties Geert Uytterhoeven
2021-06-15 19:54 ` Rob Herring
2021-06-15 23:28 ` Nick Kossifidis
2021-06-16 7:58 ` Geert Uytterhoeven
2021-06-15 18:17 ` [PATCH 2/3] riscv: Remove non-standard linux,elfcorehdr handling Geert Uytterhoeven
2021-06-15 18:40 ` Nick Kossifidis
2021-06-15 19:54 ` Rob Herring
2021-06-15 23:19 ` Nick Kossifidis
2021-06-16 7:56 ` Geert Uytterhoeven
2021-06-16 10:43 ` Nick Kossifidis
2021-06-16 14:47 ` Rob Herring
2021-07-01 2:52 ` Palmer Dabbelt
2021-07-02 15:56 ` Nick Kossifidis
2021-06-15 18:17 ` [PATCH 3/3] arm64: kdump: Remove custom linux,elfcorehdr parsing Geert Uytterhoeven
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=cover.1623780059.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=aou@eecs.berkeley.edu \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--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 NNTP newsgroup(s).