From: Yixun Lan <yixun.lan@gmail.com>
To: Nick Kossifidis <mick@ics.forth.gr>,
linux-riscv <linux-riscv@lists.infradead.org>,
Palmer Dabbelt <palmer@dabbelt.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] RISC-V: Add kexec/kdump support
Date: Wed, 7 Apr 2021 07:45:17 +0000 [thread overview]
Message-ID: <CALecT5iJjxh_0+thLVib2psF9wh7m2Ev+V99jMnFHAzO9igtYA@mail.gmail.com> (raw)
In-Reply-To: <20210405085712.1953848-1-mick@ics.forth.gr>
Hi Nick
On 4/5/21 8:57 AM, Nick Kossifidis wrote:
> This patch series adds kexec/kdump and crash kernel
> support on RISC-V. For testing the patches a patched
> version of kexec-tools is needed (still a work in
> progress) which can be found at:
>
> https://riscv.ics.forth.gr/kexec-tools-patched.tar.xz
>
> v3:
> * Rebase on newer kernel tree
> * Minor cleanups
> * Split UAPI changes to a separate patch
> * Improve / cleanup init_resources
> * Resolve Palmer's comments
>
> v2:
> * Rebase on newer kernel tree
> * Minor cleanups
> * Properly populate the ioresources tre, so that it
> can be used later on for implementing strict /dev/mem
> * Use linux,usable-memory on /memory instead of a new binding
> * USe a reserved-memory node for ELF core header
>
> Nick Kossifidis (5):
> RISC-V: Add EM_RISCV to kexec UAPI header
> RISC-V: Add kexec support
> RISC-V: Improve init_resources
> RISC-V: Add kdump support
> RISC-V: Add crash kernel support
>
> arch/riscv/Kconfig | 25 ++++
> arch/riscv/include/asm/elf.h | 6 +
> arch/riscv/include/asm/kexec.h | 54 +++++++
> arch/riscv/kernel/Makefile | 6 +
> arch/riscv/kernel/crash_dump.c | 46 ++++++
> arch/riscv/kernel/crash_save_regs.S | 56 +++++++
> arch/riscv/kernel/kexec_relocate.S | 222 ++++++++++++++++++++++++++++
> arch/riscv/kernel/machine_kexec.c | 193 ++++++++++++++++++++++++
> arch/riscv/kernel/setup.c | 113 ++++++++------
> arch/riscv/mm/init.c | 110 ++++++++++++++
> include/uapi/linux/kexec.h | 1 +
> 11 files changed, 787 insertions(+), 45 deletions(-)
> create mode 100644 arch/riscv/include/asm/kexec.h
> create mode 100644 arch/riscv/kernel/crash_dump.c
> create mode 100644 arch/riscv/kernel/crash_save_regs.S
> create mode 100644 arch/riscv/kernel/kexec_relocate.S
> create mode 100644 arch/riscv/kernel/machine_kexec.c
>
Just ask out of curiosity (maybe out of topic)..
Is crash analysis [1] capable of parsing RISC-V kdump image? No?
Or, any plan working on it?
[1] https://github.com/crash-utility/crash
Yxun Lan
next prev parent reply other threads:[~2021-04-07 7:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 8:57 [PATCH v3 0/5] RISC-V: Add kexec/kdump support Nick Kossifidis
2021-04-05 8:57 ` [PATCH v3 1/5] RISC-V: Add EM_RISCV to kexec UAPI header Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-05 8:57 ` [PATCH v3 2/5] RISC-V: Add kexec support Nick Kossifidis
2021-04-06 18:38 ` Alex Ghiti
2021-04-09 10:19 ` Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-05 8:57 ` [PATCH v3 3/5] RISC-V: Improve init_resources Nick Kossifidis
2021-04-06 7:19 ` Geert Uytterhoeven
2021-04-06 8:11 ` Nick Kossifidis
2021-04-06 8:22 ` Geert Uytterhoeven
2021-04-09 10:11 ` Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-05 8:57 ` [PATCH v3 4/5] RISC-V: Add kdump support Nick Kossifidis
2021-04-06 18:36 ` Alex Ghiti
2021-04-09 10:21 ` Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-05 8:57 ` [PATCH v3 5/5] RISC-V: Add crash kernel support Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-07 7:45 ` Yixun Lan [this message]
2021-04-07 16:29 ` [PATCH v3 0/5] RISC-V: Add kexec/kdump support Rob Herring
2021-04-09 10:02 ` Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-23 3:36 ` Nick Kossifidis
2021-04-23 3:48 ` Palmer Dabbelt
2021-04-23 3:53 ` Nick Kossifidis
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=CALecT5iJjxh_0+thLVib2psF9wh7m2Ev+V99jMnFHAzO9igtYA@mail.gmail.com \
--to=yixun.lan@gmail.com \
--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 \
/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).