Re: [PPC][Tracing] Missing syscalls:* ftrace/perf events on PowerPC vs x86
Hari Bathini <[email protected]> Wed, 18 Feb 2026 11:03:31 +0530
| Newsgroups | org.kernel.vger.linux-trace-users,org.ozlabs.lists.linuxppc-dev |
|---|---|
| Message-ID | <[email protected]> |
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/[email protected]/ > 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