From: Michael Ellerman <mpe@ellerman.id.au>
To: Michael Jeanson <mjeanson@efficios.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Michael Jeanson <mjeanson@efficios.com>,
stable@vger.kernel.org, Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Michal Suchanek <msuchanek@suse.de>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] powerpc/ftrace: fix syscall tracing on PPC64_ELF_ABI_V1
Date: Mon, 05 Dec 2022 16:34:49 +1100 [thread overview]
Message-ID: <87pmcys9ae.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20221201161442.2127231-1-mjeanson@efficios.com>
Michael Jeanson <mjeanson@efficios.com> writes:
> 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.
>
> Remove the PPC64_ELF_ABI_V1 specific version of
> arch_syscall_match_sym_name to have the same behavior across all powerpc
> variants.
This doesn't seem to work for me.
Event with it applied I still don't see anything in /sys/kernel/debug/tracing/events/syscalls
Did we break it in some other way recently?
cheers
> Fixes: 68b34588e202 ("powerpc/64/sycall: Implement syscall entry/exit logic in C")
> Cc: stable@vger.kernel.org # v5.7+
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Michael Ellerman <mpe@ellerman.id.au>
> Cc: Nicholas Piggin <npiggin@gmail.com>
> Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
> Cc: Michal Suchanek <msuchanek@suse.de>
> Cc: linuxppc-dev@lists.ozlabs.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Michael Jeanson <mjeanson@efficios.com>
> Reviewed-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> ---
> arch/powerpc/include/asm/ftrace.h | 12 ------------
> 1 file changed, 12 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/ftrace.h b/arch/powerpc/include/asm/ftrace.h
> index 3cee7115441b..e3d1f377bc5b 100644
> --- a/arch/powerpc/include/asm/ftrace.h
> +++ b/arch/powerpc/include/asm/ftrace.h
> @@ -64,17 +64,6 @@ void ftrace_graph_func(unsigned long ip, unsigned long parent_ip,
> * those.
> */
> #define ARCH_HAS_SYSCALL_MATCH_SYM_NAME
> -#ifdef CONFIG_PPC64_ELF_ABI_V1
> -static inline bool arch_syscall_match_sym_name(const char *sym, const char *name)
> -{
> - /* We need to skip past the initial dot, and the __se_sys alias */
> - return !strcmp(sym + 1, name) ||
> - (!strncmp(sym, ".__se_sys", 9) && !strcmp(sym + 6, name)) ||
> - (!strncmp(sym, ".ppc_", 5) && !strcmp(sym + 5, name + 4)) ||
> - (!strncmp(sym, ".ppc32_", 7) && !strcmp(sym + 7, name + 4)) ||
> - (!strncmp(sym, ".ppc64_", 7) && !strcmp(sym + 7, name + 4));
> -}
> -#else
> static inline bool arch_syscall_match_sym_name(const char *sym, const char *name)
> {
> return !strcmp(sym, name) ||
> @@ -83,7 +72,6 @@ static inline bool arch_syscall_match_sym_name(const char *sym, const char *name
> (!strncmp(sym, "ppc32_", 6) && !strcmp(sym + 6, name + 4)) ||
> (!strncmp(sym, "ppc64_", 6) && !strcmp(sym + 6, name + 4));
> }
> -#endif /* CONFIG_PPC64_ELF_ABI_V1 */
> #endif /* CONFIG_FTRACE_SYSCALLS */
>
> #if defined(CONFIG_PPC64) && defined(CONFIG_FUNCTION_TRACER)
> --
> 2.34.1
next prev parent reply other threads:[~2022-12-05 5:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 16:14 [PATCH] powerpc/ftrace: fix syscall tracing on PPC64_ELF_ABI_V1 Michael Jeanson
2022-12-05 5:34 ` Michael Ellerman [this message]
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
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=87pmcys9ae.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--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=msuchanek@suse.de \
--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