public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Hari Bathini <hbathini@linux.ibm.com>
To: "Nassiri, Mohammad" <mnassiri@ciena.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: "linux-trace-users@vger.kernel.org"
	<linux-trace-users@vger.kernel.org>,
	"michael@ellerman.id.au" <michael@ellerman.id.au>,
	"srostedt@redhat.com" <srostedt@redhat.com>,
	"masami.hiramatsu@linaro.org" <masami.hiramatsu@linaro.org>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PPC][Tracing] Missing syscalls:* ftrace/perf events on PowerPC vs x86
Date: Wed, 18 Feb 2026 11:03:31 +0530	[thread overview]
Message-ID: <b9ddf051-f6eb-489a-b199-6d47f5a21395@linux.ibm.com> (raw)
In-Reply-To: <CH2PR04MB6821DAF7C6684BB990A0288BC56DA@CH2PR04MB6821.namprd04.prod.outlook.com>



On 18/02/26 1:40 am, Nassiri, Mohammad wrote:
> Hello,
> 
> On PPC64 with Yocto Kirkstone and Linux 5.10.x, `CONFIG_FTRACE_SYSCALLS=y` is enabled, but neither `perf list` nor ftrace show per‑syscall events under `/sys/kernel/debug/tracing/events/syscalls`. Only `raw_syscalls:sys_enter` / `raw_syscalls:sys_exit` are available.
> 
> On the same build and kernel version for x86_64, per‑syscall events are visible.
> 
> Configs on PPC include:
> CONFIG_TRACEPOINTS=y
> CONFIG_EVENT_TRACING=y
> CONFIG_FTRACE=y
> CONFIG_FTRACE_SYSCALLS=y
> CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
> 
> Questions:
> 1. Is the absence of per‑syscall tracepoints on PPC in 5.10.x expected behaviour, or am I missing a config option required for these syscalls:* events to be available?
> 2. Or were these events only enabled for PPC after Michael Ellerman’s syscall tracing patch series in v6.1?
>     Link: https://lore.kernel.org/linuxppc-dev/166488988686.779920.13794870102696416283.b4-ty@ellerman.id.au/
> 3. If yes to (2), would a minimal backport of the PPC syscall tracepoint generation code from v6.1 allow 5.10.x to show syscalls:* events in perf/ftrace?

You should see syscall enter/exit tracepoints on v5.10.x without syscall
wrapper patchset referred above. Are you using v5.10.250 ?
Also, would help, if you can share the .config you used.

- Hari


  parent reply	other threads:[~2026-02-18  5:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 20:10 [PPC][Tracing] Missing syscalls:* ftrace/perf events on PowerPC vs x86 Nassiri, Mohammad
2026-02-17 20:23 ` Steven Rostedt
2026-02-17 20:47   ` [**EXTERNAL**] " Nassiri, Mohammad
2026-02-18  5:33 ` Hari Bathini [this message]
2026-02-18 13:56   ` Nassiri, Mohammad
2026-02-20  7:54     ` Hari Bathini
2026-02-21 17:34       ` Nassiri, Mohammad

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=b9ddf051-f6eb-489a-b199-6d47f5a21395@linux.ibm.com \
    --to=hbathini@linux.ibm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-trace-users@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=masami.hiramatsu@linaro.org \
    --cc=michael@ellerman.id.au \
    --cc=mnassiri@ciena.com \
    --cc=npiggin@gmail.com \
    --cc=srostedt@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox