From: "Michal Suchánek" <msuchanek@suse.de>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Michael Jeanson <mjeanson@efficios.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Steven Rostedt <rostedt@goodmis.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Nicholas Piggin <npiggin@gmail.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powerpc/ftrace: fix syscall tracing on PPC64_ELF_ABI_V1
Date: Wed, 7 Dec 2022 16:59:24 +0100 [thread overview]
Message-ID: <20221207155924.GG28810@kitsune.suse.cz> (raw)
In-Reply-To: <6db50470-ac37-0328-37a2-760665668b5f@efficios.com>
Hello,
On Wed, Dec 07, 2022 at 10:18:13AM -0500, Mathieu Desnoyers wrote:
> On 2022-12-06 21:09, Michael Ellerman wrote:
> > Mathieu Desnoyers <mathieu.desnoyers@efficios.com> writes:
> > > On 2022-12-05 17:50, Michael Ellerman wrote:
> >
> > Relatedly we have a patch in next to optionally use ABIv2 for 64-bit big
> > endian builds.
>
> Interesting. Does it require a matching user-space ? (built with PPC64 ABIv2
No, the kernel and userspace ABI is separate.
> ?) Does it handle legacy PPC32 executables ?
Theoretically it should. No idea if anybody has tested it.
Thanks
Michal
next prev parent reply other threads:[~2022-12-07 15:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 16:14 Michael Jeanson
2022-12-05 5:34 ` Michael Ellerman
2022-12-05 18:19 ` Michael Jeanson
2022-12-05 18:56 ` Christophe Leroy
2022-12-05 20:11 ` Michael Jeanson
2022-12-05 21:46 ` Michael Jeanson
2022-12-05 22:50 ` Michael Ellerman
2022-12-06 14:38 ` Mathieu Desnoyers
2022-12-06 23:08 ` Christophe Leroy
2022-12-07 2:09 ` Michael Ellerman
2022-12-07 15:18 ` Mathieu Desnoyers
2022-12-07 15:59 ` Michal Suchánek [this message]
2022-12-07 16:26 ` Christophe Leroy
2022-12-08 12:40 ` 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=20221207155924.GG28810@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mjeanson@efficios.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®