From: "Ryan B. Sullivan" <rysulliv@redhat.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Joe Lawrence <joe.lawrence@redhat.com>,
live-patching@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
pmladek@suse.com, mbenes@suse.cz, jikos@kernel.org,
jpoimboe@kernel.org, naveen.n.rao@linux.ibm.com,
christophe.leroy@csgroup.eu, npiggin@gmail.com
Subject: Re: [PATCH] powerpc/ftrace: restore r2 to caller's stack on livepatch sibling call
Date: Tue, 10 Sep 2024 11:02:56 -0400 [thread overview]
Message-ID: <ZuBfoBKUejKLlV5c@sullivan-work> (raw)
In-Reply-To: <87bk0wrn1m.fsf@mail.lhotse>
On Tue, Sep 10, 2024 at 05:21:57PM +1000, Michael Ellerman wrote:
> "Ryan B. Sullivan" <rysulliv@redhat.com> writes:
> > Hello all,
> >
> > Just wanted to ping and see if there was any further feedback or
> > questions regarding the patch?
>
Hi Michael,
Thank you for the update.
> Hi Ryan,
>
> I'd really like a selftest that triggers the sibling call behaviour.
>
> As I said upthread I tried writing one but failed. Which you later
> explained is because the cross-module sibling call is not generated by
> the compiler but rather by the code being objcopy'ed (or similar).
>
> I think it should be possible to trick the compiler into letting us do a
> cross-module sibling call by doing it in an inline asm block. Obviously
> that's non-standard, but I think it might work well enough for a test?
>
> We have an example of calling a function within an inline asm block in
> call_do_irq().
If you think that that would be a welcome addition to the patch I can
look into adding it, especially if you are busy at the moment.
>
> I'll try to find time to get that done, but I can't promise when.
>
> cheers
>
Cheers,
Ryan
next prev parent reply other threads:[~2024-09-10 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 18:33 [PATCH] powerpc/ftrace: restore r2 to caller's stack on livepatch sibling call Ryan Sullivan
2024-07-24 18:33 ` Ryan Sullivan
2024-07-29 14:17 ` Michael Ellerman
2024-07-29 14:17 ` Michael Ellerman
2024-07-29 15:02 ` Ryan Sullivan
2024-07-29 15:02 ` Ryan Sullivan
2024-08-15 10:22 ` Michael Ellerman
2024-08-15 16:07 ` Ryan Sullivan
2024-08-15 16:24 ` Joe Lawrence
2024-09-09 16:33 ` Ryan B. Sullivan
2024-09-10 7:21 ` Michael Ellerman
2024-09-10 15:02 ` Ryan B. Sullivan [this message]
2024-08-08 7:00 ` Christophe Leroy
2024-08-08 7:00 ` Christophe Leroy
2024-08-08 17:55 ` [PATCH v2] powerpc/ftrace: restore caller's toc on ppc64 " Ryan Sullivan
2024-08-08 17:55 ` Ryan Sullivan
2024-08-08 21:17 ` Ryan Sullivan
2024-08-08 21:17 ` Ryan Sullivan
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=ZuBfoBKUejKLlV5c@sullivan-work \
--to=rysulliv@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=pmladek@suse.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.