From: Petr Tesarik <petrtesarik@huaweicloud.com>
To: kexec@lists.infradead.org
Subject: [PATCH v1 0/3] RISC-V: Fix a few kexec_file_load(2) failures
Date: Tue, 25 Jul 2023 12:01:07 +0200 [thread overview]
Message-ID: <cover.1690274483.git.petr.tesarik.ext@huawei.com> (raw)
From: Petr Tesarik <petr.tesarik.ext@huawei.com>
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 additional relocation types and removes the need
to implement a Global Offset Table (GOT) for the purgatory.
Petr Tesarik (2):
riscv/kexec: handle R_RISCV_ADD16 and R_RISCV_SUB16 relocation types
riscv/purgatory: do not link with string.o
Torsten Duwe (1):
riscv/kexec: handle R_RISCV_CALL_PLT relocation type
arch/riscv/kernel/elf_kexec.c | 7 +++++++
arch/riscv/purgatory/Makefile | 9 +--------
2 files changed, 8 insertions(+), 8 deletions(-)
--
2.25.1
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2023-07-25 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 10:01 Petr Tesarik [this message]
2023-07-25 10:01 ` [PATCH v1 1/3] riscv/kexec: handle R_RISCV_CALL_PLT relocation type Petr Tesarik
2023-07-25 10:01 ` [PATCH v1 2/3] riscv/kexec: handle R_RISCV_ADD16 and R_RISCV_SUB16 relocation types Petr Tesarik
2023-07-25 10:01 ` [PATCH v1 3/3] riscv/purgatory: do not link with string.o Petr Tesarik
2023-07-25 10:06 ` [PATCH v1 0/3] RISC-V: Fix a few kexec_file_load(2) failures Petr Tesařík
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=cover.1690274483.git.petr.tesarik.ext@huawei.com \
--to=petrtesarik@huaweicloud.com \
--cc=kexec@lists.infradead.org \
/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