All of
 help / color / mirror / Atom feed
From: "Nicholas Piggin" <>
To: "Christophe Leroy" <>,
	"" <>
Subject: Re: [RFC PATCH 4/4] powerpc/64: Remove support for kernel's built with ELFv1 ABI
Date: Tue, 09 May 2023 18:25:18 +1000	[thread overview]
Message-ID: <CSHLQGQA5FL9.2Y9YRT25EOJ0W@wheely> (raw)
In-Reply-To: <>

On Fri May 5, 2023 at 6:49 PM AEST, Christophe Leroy wrote:
> Le 05/05/2023 à 09:18, Nicholas Piggin a écrit :
> > User code must still support ELFv1, e.g., see is_elf2_task().
> > 
> > This one should wait a while until ELFv2 fallout settles, so
> > just posting it out of interest.
> Can't ELFv1 user code run on an ELFv2 kernel ?

Yes it can and that's what ELFv2 BE kernels do because most BE userspace
is ELFv1 (although some are using ELFv2 BE).

By ELFv2 fallout I mean bugs and toolchain problems that might get
discovered after we flip the default. I think it would be good to keep
the ELFv1 option around for a few releases to help testing such issues,
the revert will probably pick up conflicts. Maybe that's being too


  reply	other threads:[~2023-05-09  8:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05  7:18 [PATCH 0/4] powerpc/64: ELFv2 conversion Nicholas Piggin
2023-05-05  7:18 ` [PATCH 1/4] powerpc/64: Force ELFv2 when building with LLVM linker Nicholas Piggin
2023-05-05 21:39   ` Nathan Chancellor
2023-05-05 21:39     ` Nathan Chancellor
2023-05-05  7:18 ` [PATCH 2/4] powerpc/64: Make ELFv2 the default for big-endian builds Nicholas Piggin
2023-05-05  7:18 ` [PATCH 3/4] powerpc/64s: Remove support for ELFv1 little endian userspace Nicholas Piggin
2023-05-05  7:18 ` [RFC PATCH 4/4] powerpc/64: Remove support for kernel's built with ELFv1 ABI Nicholas Piggin
2023-05-05  8:49   ` Christophe Leroy
2023-05-09  8:25     ` Nicholas Piggin [this message]
2023-05-05  8:51 ` [PATCH 0/4] powerpc/64: ELFv2 conversion Christophe Leroy
2023-05-05 12:21   ` Michael Ellerman
2023-05-05 15:08     ` Naveen N. Rao

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CSHLQGQA5FL9.2Y9YRT25EOJ0W@wheely \ \ \ \

* 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.