[PPC][Tracing] Missing syscalls:* ftrace/perf events on PowerPC vs x86

Hari Bathini hbathini at linux.ibm.com
Wed Feb 18 16:33:31 AEDT 2026



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


More information about the Linuxppc-dev mailing list