Hi, On 7/26/2023 11:53 AM, Petr Tesarik wrote: > From: Petr Tesarik <petr.tesarik.ext@xxxxxxxxxx> > > The kexec_file_load(2) syscall does not work at least in some kernel > builds. For details see the relevant section in this blog post: > > https://sigillatum.tesarici.cz/2023-07-21-state-of-riscv64-kdump.html > > This patch series handles an additional relocation types, removes the need > to implement a Global Offset Table (GOT) for the purgatory and fixes the > placement of initrd. It seems there are no objections, but what is the plan here? Take it into 6.5 as a fix, or let it go through for-next? Petr T > Changelog > ========= > > Changes from v1: > - Replace memcmp() with a for loop. > - Drop handling of 16-bit add/subtract relocations. They were used only > by alternatives in strcmp(), which was referenced only by string.o. > - Add the initrd placement fix. > > Petr Tesarik (1): > riscv/purgatory: do not link with string.o and its dependencies > > Torsten Duwe (2): > riscv/kexec: handle R_RISCV_CALL_PLT relocation type > riscv/kexec: load initrd high in available memory > > arch/riscv/kernel/elf_kexec.c | 3 ++- > arch/riscv/purgatory/Makefile | 26 +------------------------- > arch/riscv/purgatory/purgatory.c | 6 ++++-- > 3 files changed, 7 insertions(+), 28 deletions(-) > _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
