From: Michael Ellerman <mpe@ellerman.id.au>
To: Geoff Levand <geoff@infradead.org>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/ps3_defconfig: Disable PPC64_BIG_ENDIAN_ELF_ABI_V2
Date: Wed, 27 Dec 2023 12:27:58 +1100 [thread overview]
Message-ID: <87zfxwjuxt.fsf@mail.lhotse> (raw)
In-Reply-To: <df906ac1-5f17-44b9-b0bb-7cd292a0df65@infradead.org>
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.
> This change just adds the line '# CONFIG_PPC64_BIG_ENDIAN_ELF_ABI_V2 is not set'
> to the ps3_defconfig file so that the PPC64_ELF_ABI_V1 is used.
>
> Fixes run time errors like these:
>
> BUG: Kernel NULL pointer dereference at 0x00000000
> Faulting instruction address: 0xc000000000047cf0
> Oops: Kernel access of bad area, sig: 11 [#1]
>
> Call Trace:
> [c0000000023039e0] [c00000000100ebfc] ps3_create_spu+0xc4/0x2b0 (unreliable)
> [c000000002303ab0] [c00000000100d4c4] create_spu+0xcc/0x3c4
> [c000000002303b40] [c00000000100eae4] ps3_enumerate_spus+0xa4/0xf8
That can't be the first hvcall we've done, there's one in
ps3_setup_arch(). So I guess only some hcalls are failing?
cheers
next prev parent reply other threads:[~2023-12-27 1:28 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 [this message]
2023-12-27 9:44 ` Geoff Levand
2024-01-09 8:55 ` Geert Uytterhoeven
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=87zfxwjuxt.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=geoff@infradead.org \
--cc=linuxppc-dev@lists.ozlabs.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 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.