[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167050321063.1457988.11365233998356574445.b4-ty@ellerman.id.au>
Date: Thu, 08 Dec 2022 23:40:10 +1100
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: Steven Rostedt <rostedt@...dmis.org>,
Michael Jeanson <mjeanson@...icios.com>
Cc: Nicholas Piggin <npiggin@...il.com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Michael Ellerman <mpe@...erman.id.au>,
Masami Hiramatsu <mhiramat@...nel.org>, stable@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Mark Rutland <mark.rutland@....com>,
Michal Suchanek <msuchanek@...e.de>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] powerpc/ftrace: fix syscall tracing on PPC64_ELF_ABI_V1
On Thu, 1 Dec 2022 11:14:42 -0500, Michael Jeanson wrote:
> In v5.7 the powerpc syscall entry/exit logic was rewritten in C, on
> PPC64_ELF_ABI_V1 this resulted in the symbols in the syscall table
> changing from their dot prefixed variant to the non-prefixed ones.
>
> Since ftrace prefixes a dot to the syscall names when matching them to
> build its syscall event list, this resulted in no syscall events being
> available.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/ftrace: fix syscall tracing on PPC64_ELF_ABI_V1
https://git.kernel.org/powerpc/c/ad050d2390fccb22aa3e6f65e11757ce7a5a7ca5
cheers
Powered by blists - more mailing lists