From: Geoff Levand <geoff@infradead.org>
To: Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH 0/3] powerpc/ps3: Fixes for lv1 hcall assembly
Date: Fri, 29 Dec 2023 17:53:01 +0900 [thread overview]
Message-ID: <8991a6d9-bf19-4c15-9803-3238cb41aa80@infradead.org> (raw)
In-Reply-To: <ddfd8c20-0bc8-4373-b7a5-27dd2d00ee69@infradead.org>
Hi Nick,
On 12/27/23 18:50, Geoff Levand wrote:
>> Nicholas Piggin (3):
>> powerpc/ps3: Fix lv1 hcall assembly for ELFv2 calling convention
>> powerpc/ps3: lv1 hcall code use symbolic constant for LR save offset
>> powerpc/ps3: Make real stack frames for LV1 hcalls
I tested these patches applied to v6.7-rc7 on PS3 with
CONFIG_PPC64_BIG_ENDIAN_ELF_ABI_V2=y, and they seem to be working OK. I did
not do any extensive testing though.
I tested three configurations:
- With only the first patch 'Fix lv1 hcall assembly for ELFv2 calling
convention' applied.
- With the first two patches, 'Fix lv1 hcall assembly for ELFv2 calling
convention' and 'lv1 hcall code use symbolic constant for LR save
offset' applied.
- And with all three patches applied.
All three configurations worked OK. Thanks again for working on this.
Michael, I think we can just add these three patches and remove my patch that
disables CONFIG_PPC64_BIG_ENDIAN_ELF_ABI_V2.
Tested-by: Geoff Levand <geoff@infradead.org>
next prev parent reply other threads:[~2023-12-29 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 7:24 [PATCH 0/3] powerpc/ps3: Fixes for lv1 hcall assembly Nicholas Piggin
2023-12-27 7:24 ` [PATCH 1/3] powerpc/ps3: Fix lv1 hcall assembly for ELFv2 calling convention Nicholas Piggin
2023-12-27 7:24 ` [PATCH 2/3] powerpc/ps3: lv1 hcall code use symbolic constant for LR save offset Nicholas Piggin
2023-12-27 7:24 ` [PATCH 3/3] powerpc/ps3: Make real stack frames for LV1 hcalls Nicholas Piggin
2023-12-27 9:50 ` [PATCH 0/3] powerpc/ps3: Fixes for lv1 hcall assembly Geoff Levand
2023-12-29 8:53 ` Geoff Levand [this message]
2024-02-26 5:56 ` 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=8991a6d9-bf19-4c15-9803-3238cb41aa80@infradead.org \
--to=geoff@infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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).