Re: [PATCH 0/7] Kexec-tools: Improve RISC-V port

[Nick Kossifidis <mick@ics.forth.gr>]

On 9/15/23 06:50, 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.
> 
> 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
> 

A few years back I did the initial work for kexec on riscv, and the idea 
was to work on the kexec-tools repo on riscv github:

https://github.com/riscv-collab/kexec-tools/tree/riscv

and then when we have something in a good shape, to push our work 
upstream. People keep sending patches to the kexec mailing list (the 
riscv port of kexec-tools is not upstream so this patch series won't 
apply), instead of pull requests to the above repo.

You have an X set of updates, some other people have posted another set 
of fixes (e.g. I rememver a fix for initramfs/initrd), please let's work 
on the github repo, get something that looks ok and then push our work 
upstream. If you want access to the github repo instead of doing pull 
requests etc let me know.

I'm sorry I didn't have the time to work on this further.

Regards,
Nick

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec