* [Bug bpf/24656] New: Target variables for tracepoints differ between traditional sytemtap backend and bpf backend
@ 2019-06-10 14:35 wcohen at redhat dot com
2019-06-10 14:53 ` [Bug bpf/24656] " fche at redhat dot com
0 siblings, 1 reply; 2+ messages in thread
From: wcohen at redhat dot com @ 2019-06-10 14:35 UTC (permalink / raw)
To: systemtap
https://sourceware.org/bugzilla/show_bug.cgi?id=24656
Bug ID: 24656
Summary: Target variables for tracepoints differ between
traditional sytemtap backend and bpf backend
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: bpf
Assignee: systemtap at sourceware dot org
Reporter: wcohen at redhat dot com
Target Milestone: ---
After getting the target() function working I expected that the cycle_thief.stp
example would work with the bpf backend. However, found that the bpf backend
has a different set of target variables available than the original systemtap
kernel module backend:
[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
Did not see this type of difference between probes for a kernel function. For
example the vfs_read probes are the same:
[wcohen@localhost systemtap]$ ../install/bin/stap -L
'kernel.function("vfs_read")'
kernel.function("vfs_read@fs/read_write.c:446") $file:struct file* $buf:char*
$count:size_t $pos:loff_t*
[wcohen@localhost systemtap]$ ../install/bin/stap --bpf -L
'kernel.function("vfs_read")'
kernel.function("vfs_read@fs/read_write.c:446") $file:struct file* $buf:char*
$count:size_t $pos:loff_t*
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug bpf/24656] Target variables for tracepoints differ between traditional sytemtap backend and bpf backend
2019-06-10 14:35 [Bug bpf/24656] New: Target variables for tracepoints differ between traditional sytemtap backend and bpf backend wcohen at redhat dot com
@ 2019-06-10 14:53 ` fche at redhat dot com
0 siblings, 0 replies; 2+ messages in thread
From: fche at redhat dot com @ 2019-06-10 14:53 UTC (permalink / raw)
To: systemtap
https://sourceware.org/bugzilla/show_bug.cgi?id=24656
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |fche at redhat dot com
Resolution|--- |DUPLICATE
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
dupe
*** This bug has been marked as a duplicate of bug 23866 ***
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-06-10 14:53 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-10 14:35 [Bug bpf/24656] New: Target variables for tracepoints differ between traditional sytemtap backend and bpf backend wcohen at redhat dot com
2019-06-10 14:53 ` [Bug bpf/24656] " fche at redhat dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).