mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Jeanson <mjeanson@efficios.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Nicholas Piggin <npiggin@gmail.com>,
	Michal Suchanek <msuchanek@suse.de>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.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, 5 Dec 2022 15:11:07 -0500	[thread overview]
Message-ID: <323f83c7-38fe-8a12-d77a-0a7249aad316@efficios.com> (raw)
In-Reply-To: <219580de-7473-f142-5ef2-1ed40e41d13d@csgroup.eu>

On 2022-12-05 13:56, Christophe Leroy wrote:
> 
> 
> Le 05/12/2022 à 19:19, Michael Jeanson a écrit :
>> [Vous ne recevez pas souvent de courriers de mjeanson@efficios.com.
>> Découvrez pourquoi ceci est important à
>> https://aka.ms/LearnAboutSenderIdentification ]
>>
>> On 2022-12-05 00:34, Michael Ellerman wrote:
>>> 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
>>
>> I've just tried this change on top of v6.1-rc8 in qemu with a base
>> config of
>> 'corenet32_smp_defconfig' and these options on top:
>>
>> CONFIG_FTRACE=y
>> CONFIG_FTRACE_SYSCALLS=y
>>
>> And I can trace syscalls with ftrace.
>>
>> What kernel tree and config are you using?
> 
> If you are using a ppc32 config, CONFIG_PPC64_ELF_ABI_V1 won't be set,
> so it doesn't matter whether this change is there or not.
> 
> You should try corenet64_smp_defconfig if you want
> CONFIG_PPC64_ELF_ABI_V1 to be set.
> 
> You can also use ppc64_defconfig, that's a different platform but it
> also has CONFIG_PPC64_ELF_ABI_V1.

You are absolutely right, I used the wrong environment, I blame Monday 
morning. I tested again this time using 'corenet64_smp_defconfig' with the 
same options and syscall tracing with ftrace also works.

I double checked that /proc/config.gz contained CONFIG_PPC64_ELF_ABI_V1 to be 
sure.

> 
> Christophe
> 
>>
>> Thanks for looking into this.
>>


  reply	other threads:[~2022-12-05 20:11 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 [this message]
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=323f83c7-38fe-8a12-d77a-0a7249aad316@efficios.com \
    --to=mjeanson@efficios.com \
    --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=mpe@ellerman.id.au \
    --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

all inboxes | Powered by JetHome®