From: Simon Horman <horms@kernel.org>
To: Song Shuai <songshuaishuai@tinylab.org>
Cc: lizhengyu3@huawei.com, liaochang1@huawei.com,
xianting.tian@linux.alibaba.com, guoren@kernel.org,
huanyi.xj@alibaba-inc.com, mick@ics.forth.gr,
yixun.lan@gmail.com, kexec@lists.infradead.org
Subject: Re: [PATCH 0/7] Kexec-tools: Improve RISC-V port
Date: Wed, 20 Sep 2023 12:56:34 +0100 [thread overview]
Message-ID: <20230920115634.GG224399@kernel.org> (raw)
In-Reply-To: <20230915035013.1582679-1-songshuaishuai@tinylab.org>
On Fri, Sep 15, 2023 at 11:50:06AM +0800, Song Shuai wrote:
> Hi,
>
> This series is created to improve RISC-V port of kexec-tools,
> and is based on the horms/kexec-tools:build-test-riscv-v2 branch.
In my mind the big question is how to move RISC-V support
from that branch, to being merged into main.
IIRC there were some issues that needed to be addressed.
Perhaps they are all addressed by this series, and with
some appropriate squashing we can move forwards with a series
based on main?
>
> For your convenience, here is my Github branch for kexec-tools:
> https://github.com/sugarfillet/kexec-tools/commits/rv-Image
>
> The first four patches fixes some build or runtime issues:
>
> RISC-V: Use linux,usable-memory-range for crash kernel
> RISC-V: Fix the undeclared ‘EM_RISCV’ build failure
> RISC-V: Get memory ranges from iomem
> RISC-V: Correct the usage of command line option
>
> The last three patches enable the kexec_file_load syscall to load
> vmlinux and support loading Image binary file for two syscalls.
>
> RISC-V: Enable kexe_file_load
> RISC-V: Separate elf_riscv_find_pbase out
> RISC-V: Support loading Image binary file
>
> Note that:
>
> RISC-V Linux kexec_load_file's support for Image file has been sent out but not merged [1].
>
> [1]: https://lore.kernel.org/linux-riscv/20230914020044.1397356-1-songshuaishuai@tinylab.org/T/#t
>
> Li Zhengyu (1):
> RISC-V: Enable kexe_file_load
>
> Song Shuai (6):
> RISC-V: Use linux,usable-memory-range for crash kernel
> RISC-V: Fix the undeclared ‘EM_RISCV’ build failure
> RISC-V: Get memory ranges from iomem
> RISC-V: Correct the usage of command line option
> RISC-V: Separate elf_riscv_find_pbase out
> RISC-V: Support loading Image binary file
>
> kexec/arch/riscv/Makefile | 2 +
> kexec/arch/riscv/crashdump-riscv.c | 2 +-
> kexec/arch/riscv/image-header.h | 88 ++++++++++++++
> kexec/arch/riscv/iomem.h | 10 ++
> kexec/arch/riscv/kexec-elf-riscv.c | 77 +-----------
> kexec/arch/riscv/kexec-image-riscv.c | 95 +++++++++++++++
> kexec/arch/riscv/kexec-riscv.c | 176 ++++++++++++++++++++++-----
> kexec/arch/riscv/kexec-riscv.h | 21 ++++
> kexec/kexec-syscall.h | 3 +
> 9 files changed, 368 insertions(+), 106 deletions(-)
> create mode 100644 kexec/arch/riscv/image-header.h
> create mode 100644 kexec/arch/riscv/iomem.h
> create mode 100644 kexec/arch/riscv/kexec-image-riscv.c
>
> --
> 2.20.1
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2023-09-20 11:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 3:50 [PATCH 0/7] Kexec-tools: Improve RISC-V port Song Shuai
2023-09-15 3:50 ` [PATCH 1/7] RISC-V: Use linux,usable-memory-range for crash kernel Song Shuai
2023-09-15 3:50 ` [PATCH 2/7] RISC-V: Fix the undeclared ‘EM_RISCV’ build failure Song Shuai
2023-09-15 3:50 ` [PATCH 3/7] RISC-V: Get memory ranges from iomem Song Shuai
2023-09-15 3:50 ` [PATCH 4/7] RISC-V: Correct the usage of command line option Song Shuai
2023-09-15 3:50 ` [PATCH 5/7] RISC-V: Enable kexe_file_load Song Shuai
2023-09-15 3:50 ` [PATCH 6/7] RISC-V: Separate elf_riscv_find_pbase out Song Shuai
2023-09-15 3:50 ` [PATCH 7/7] RISC-V: Support loading Image binary file Song Shuai
2023-09-20 11:56 ` Simon Horman [this message]
2023-10-11 5:22 ` [PATCH 0/7] Kexec-tools: Improve RISC-V port Song Shuai
2024-05-18 3:39 ` Dave Young
2024-05-18 8:33 ` Simon Horman
2024-08-12 14:36 ` Petr Tesarik
2024-08-13 14:26 ` Simon Horman
2024-08-14 8:23 ` Dave Young
2025-01-10 9:22 ` Dave Young
2023-09-20 13:47 ` 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=20230920115634.GG224399@kernel.org \
--to=horms@kernel.org \
--cc=guoren@kernel.org \
--cc=huanyi.xj@alibaba-inc.com \
--cc=kexec@lists.infradead.org \
--cc=liaochang1@huawei.com \
--cc=lizhengyu3@huawei.com \
--cc=mick@ics.forth.gr \
--cc=songshuaishuai@tinylab.org \
--cc=xianting.tian@linux.alibaba.com \
--cc=yixun.lan@gmail.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