From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: "Naveen N . Rao" <naveen.n.rao@linux.vnet.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH v2 0/4] powerpc/64: ELFv2 conversion
Date: Tue, 6 Jun 2023 19:38:28 +1000 [thread overview]
Message-ID: <20230606093832.199712-1-npiggin@gmail.com> (raw)
This is a follow on from the series here
https://lore.kernel.org/linuxppc-dev/20230505071850.228734-1-npiggin@gmail.com/
With feedback addressed and Christophe's -mprofile-kernel for BE added,
https://lore.kernel.org/linuxppc-dev/20230506011814.8766-1-npiggin@gmail.com/
And dropped the last RFC patch that removes ELFv1 entirely. Maybe we can
wait one or two releases after this before doing that.
Thanks,
Nick
Nicholas Piggin (4):
powerpc/64: Force ELFv2 when building with LLVM linker
powerpc/64: Make ELFv2 the default for big-endian builds
powerpc/64: Use -mprofile-kernel for big endian ELFv2 kernels
powerpc/64s: Remove support for ELFv1 little endian userspace
arch/powerpc/Kconfig | 13 +++++++------
arch/powerpc/include/asm/elf.h | 6 ++++++
arch/powerpc/include/asm/thread_info.h | 6 +++++-
arch/powerpc/tools/gcc-check-mprofile-kernel.sh | 11 ++++++-----
4 files changed, 24 insertions(+), 12 deletions(-)
--
2.40.1
next reply other threads:[~2023-06-06 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 9:38 Nicholas Piggin [this message]
2023-06-06 9:38 ` [PATCH v2 1/4] powerpc/64: Force ELFv2 when building with LLVM linker Nicholas Piggin
2023-06-06 9:38 ` [PATCH v2 2/4] powerpc/64: Make ELFv2 the default for big-endian builds Nicholas Piggin
2023-06-06 9:38 ` [PATCH v2 3/4] powerpc/64: Use -mprofile-kernel for big endian ELFv2 kernels Nicholas Piggin
2023-06-06 9:38 ` [PATCH v2 4/4] powerpc/64s: Remove support for ELFv1 little endian userspace Nicholas Piggin
2023-07-03 5:26 ` [PATCH v2 0/4] powerpc/64: ELFv2 conversion Michael Ellerman
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=20230606093832.199712-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.