From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: kexec@lists.infradead.org
Cc: linuxppc-dev@lists.ozlabs.org, deller@gmx.de,
Sven Schnelle <svens@stackframe.org>
Subject: Re: [PATCH v4 0/7] kexec: add generic support for elf kernel images
Date: Tue, 20 Aug 2019 22:11:25 -0300 [thread overview]
Message-ID: <87pnkzmif6.fsf@morokweng.localdomain> (raw)
In-Reply-To: <20190715082702.27308-1-svens@stackframe.org>
Sven Schnelle <svens@stackframe.org> writes:
> Changes to v3:
> - add support for 32-bit ELF files
>
> Changes to v2:
> - use git format-patch -C
>
> Changes to v1:
> - split up patch into smaller pieces
> - rebase onto powerpc/next
> - remove unused variable in kexec_elf_load()
>
> Changes to RFC version:
> - remove unused Elf_Rel macro
> - remove section header parsing
> - remove PURGATORY_STACK_SIZE
> - change order of elf_*_to_cpu() functions
> - remove elf_addr_to_cpu macro
>
> Sven Schnelle (7):
> kexec: add KEXEC_ELF
> kexec_elf: change order of elf_*_to_cpu() functions
> kexec_elf: remove parsing of section headers
> kexec_elf: remove PURGATORY_STACK_SIZE
> kexec_elf: remove Elf_Rel macro
> kexec_elf: remove unused variable in kexec_elf_load()
> kexec_elf: support 32 bit ELF files
>
> arch/Kconfig | 3 +
> arch/powerpc/Kconfig | 1 +
> arch/powerpc/kernel/kexec_elf_64.c | 551 +----------------------------
> include/linux/kexec.h | 23 ++
> kernel/Makefile | 1 +
> kernel/kexec_elf.c | 418 ++++++++++++++++++++++
> 6 files changed, 456 insertions(+), 541 deletions(-)
> create mode 100644 kernel/kexec_elf.c
The series applies on v5.1 but not newer kernels, so it needs to be
rebased.
I tested with v5.1 in ppc64le kexecing to both little-endian and
big-endian kernels, and also in ppc64 kexecing to both big-endian and
little-endian kernels so:
Tested-by: Thiago Jung Bauermann <bauerman@linux.ibm.com>
--
Thiago Jung Bauermann
IBM Linux Technology Center
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2019-08-21 1:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 8:26 [PATCH v4 0/7] kexec: add generic support for elf kernel images Sven Schnelle
2019-07-15 8:26 ` [PATCH v4 1/7] kexec: add KEXEC_ELF Sven Schnelle
2019-08-21 0:58 ` Thiago Jung Bauermann
2019-08-21 20:15 ` Thiago Jung Bauermann
2019-07-15 8:26 ` [PATCH v4 2/7] kexec_elf: change order of elf_*_to_cpu() functions Sven Schnelle
2019-08-21 0:59 ` Thiago Jung Bauermann
2019-07-15 8:26 ` [PATCH v4 3/7] kexec_elf: remove parsing of section headers Sven Schnelle
2019-08-21 0:59 ` Thiago Jung Bauermann
2019-07-15 8:26 ` [PATCH v4 4/7] kexec_elf: remove PURGATORY_STACK_SIZE Sven Schnelle
2019-08-21 1:00 ` Thiago Jung Bauermann
2019-08-21 1:13 ` Thiago Jung Bauermann
2019-07-15 8:27 ` [PATCH v4 5/7] kexec_elf: remove Elf_Rel macro Sven Schnelle
2019-08-21 1:01 ` Thiago Jung Bauermann
2019-07-15 8:27 ` [PATCH v4 6/7] kexec_elf: remove unused variable in kexec_elf_load() Sven Schnelle
2019-08-21 1:02 ` Thiago Jung Bauermann
2019-07-15 8:27 ` [PATCH v4 7/7] kexec_elf: support 32 bit ELF files Sven Schnelle
2019-08-21 1:03 ` Thiago Jung Bauermann
2019-08-21 1:11 ` Thiago Jung Bauermann [this message]
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=87pnkzmif6.fsf@morokweng.localdomain \
--to=bauerman@linux.ibm.com \
--cc=deller@gmx.de \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=svens@stackframe.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