Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210405085712.1953848-1-mick@ics.forth.gr>
In-Reply-To: <20210405085712.1953848-1-mick@ics.forth.gr>
From:   Yixun Lan <yixun.lan@gmail.com>
Date:   Wed, 7 Apr 2021 07:45:17 +0000
Message-ID: <CALecT5iJjxh_0+thLVib2psF9wh7m2Ev+V99jMnFHAzO9igtYA@mail.gmail.com>
Subject: Re: [PATCH v3 0/5] RISC-V: Add kexec/kdump support
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>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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