[Bug translator/23866] dissonance between kernel tracepoint parametrization, lkm vs bpf
wcohen at redhat dot com
sourceware-bugzilla@sourceware.org
Mon Jun 10 15:58:00 GMT 2019
https://sourceware.org/bugzilla/show_bug.cgi?id=23866
--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
Simple example of differences between the lkm and bpf backends target variable:
[wcohen@localhost systemtap]$ ../install/bin/stap -L
'kernel.trace("sched_switch")'
kernel.trace("sched:sched_switch") $preempt:bool $prev:struct task_struct*
$next:struct task_struct*
[wcohen@localhost systemtap]$ ../install/bin/stap --bpf -L
'kernel.trace("sched_switch")'
kernel.trace("sched:sched_switch") $prev_comm:char[] $prev_pid:pid_t
$prev_prio:int $prev_state:long int $next_comm:char[] $next_pid:pid_t
$next_prio:int
The cycle_thief.stp example is affected by this as it uses the
kernel.trace("sched_switch") probe point.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Systemtap
mailing list