This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/23866] dissonance between kernel tracepoint parametrization, lkm vs bpf
- From: "wcohen at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 10 Jun 2019 15:58:14 +0000
- Subject: [Bug translator/23866] dissonance between kernel tracepoint parametrization, lkm vs bpf
- Auto-submitted: auto-generated
- References: <bug-23866-6586@http.sourceware.org/bugzilla/>
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.