From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Geoff Levand <geoff@infradead.org>
Cc: linuxppc-dev@lists.ozlabs.org, Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH] powerpc/ps3_defconfig: Disable PPC64_BIG_ENDIAN_ELF_ABI_V2
Date: Tue, 9 Jan 2024 09:55:10 +0100 (CET) [thread overview]
Message-ID: <999fb114-7c46-50aa-1f64-a9d421f35897@linux-m68k.org> (raw)
In-Reply-To: <3daebc86-abbf-4f37-8268-0e2a4fefede9@infradead.org>
Hi Geoff,
On Wed, 27 Dec 2023, Geoff Levand wrote:
> On 12/27/23 10:27, Michael Ellerman wrote:
>> Geoff Levand <geoff@infradead.org> writes:
>>> Commit 8c5fa3b5c4df3d071dab42b04b971df370d99354 (powerpc/64: Make ELFv2 the
>>> default for big-endian builds), merged in Linux-6.5-rc1 changes the calling ABI
>>> in a way that is incompatible with the current code for the PS3's LV1 hypervisor
>>> calls.
>>
>> I'll take this for now.
>>
>> But medium term we would like to switch to only using ELFv2, so it would
>> be good if we can work out what the actual problem is.
>
> I've been looking into converting the LV1 hypercalls to v2.
Until then, you may want to add "depends on !CONFIG_PPC64_BIG_ENDIAN_ELF_ABI_V2"
to config PPC_PS3.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-01-09 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-24 0:52 [PATCH] powerpc/ps3_defconfig: Disable PPC64_BIG_ENDIAN_ELF_ABI_V2 Geoff Levand
2023-12-27 1:27 ` Michael Ellerman
2023-12-27 9:44 ` Geoff Levand
2024-01-09 8:55 ` Geert Uytterhoeven [this message]
2023-12-31 11:07 ` 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=999fb114-7c46-50aa-1f64-a9d421f35897@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=geoff@infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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 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).