From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: "Michal Suchánek" <msuchanek@suse.de>,
linux-kernel@vger.kernel.org,
"Nicholas Piggin" <npiggin@gmail.com>,
"Jessica Yu" <jeyu@kernel.org>
Subject: [PATCH v4 0/2] powerpc/64: Option to use ELF V2 ABI for big-endian
Date: Fri, 11 Jun 2021 19:39:57 +1000 [thread overview]
Message-ID: <20210611093959.821525-1-npiggin@gmail.com> (raw)
Since v3 I added Michael's module check for ELF ABI level. This requires
a change to core module code. If Jessica is happy with it it could go
via the powerpc tree.
Thanks,
Nick
Nicholas Piggin (2):
module: add elf_check_module_arch for module specific elf arch checks
powerpc/64: Option to use ELF V2 ABI for big-endian kernels
arch/powerpc/Kconfig | 22 ++++++++++++++++++++++
arch/powerpc/Makefile | 18 ++++++++++++------
arch/powerpc/boot/Makefile | 4 +++-
arch/powerpc/include/asm/module.h | 24 ++++++++++++++++++++++++
arch/powerpc/kernel/vdso64/Makefile | 13 +++++++++++++
drivers/crypto/vmx/Makefile | 8 ++++++--
drivers/crypto/vmx/ppc-xlate.pl | 10 ++++++----
include/linux/moduleloader.h | 5 +++++
kernel/module.c | 2 +-
9 files changed, 92 insertions(+), 14 deletions(-)
--
2.23.0
next reply other threads:[~2021-06-11 9:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 9:39 Nicholas Piggin [this message]
2021-06-11 9:39 ` [PATCH v4 1/2] module: add elf_check_module_arch for module specific elf arch checks Nicholas Piggin
2021-06-14 12:06 ` Jessica Yu
2021-06-15 2:05 ` Nicholas Piggin
2021-06-15 12:17 ` Jessica Yu
2021-06-15 12:50 ` Segher Boessenkool
2021-06-15 13:41 ` Jessica Yu
2021-06-15 14:30 ` Segher Boessenkool
2021-06-16 2:39 ` Michael Ellerman
2021-06-16 1:18 ` Nicholas Piggin
2021-06-16 12:54 ` Jessica Yu
2021-06-17 5:21 ` Nicholas Piggin
2021-06-16 2:37 ` Michael Ellerman
2021-06-16 13:49 ` Jessica Yu
2021-06-11 9:39 ` [PATCH v4 2/2] powerpc/64: Option to use ELF V2 ABI for big-endian kernels Nicholas Piggin
2021-06-11 9:58 ` Michal Suchánek
2021-06-11 10:20 ` Michal Suchánek
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=20210611093959.821525-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).