* [Bug tapsets/14690] New: the syscall tapsets could be written to prefer the 'syscalls' tracepoints
@ 2012-10-09 19:41 dsmith at redhat dot com
2012-10-09 20:14 ` [Bug tapsets/14690] " jistone at redhat dot com
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: dsmith at redhat dot com @ 2012-10-09 19:41 UTC (permalink / raw)
To: systemtap
http://sourceware.org/bugzilla/show_bug.cgi?id=14690
Bug #: 14690
Summary: the syscall tapsets could be written to prefer the
'syscalls' tracepoints
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap@sourceware.org
ReportedBy: dsmith@redhat.com
Depends on: 14689
Classification: Unclassified
If systemtap could find the 'syscalls' set of tracepoints, the syscall tapsets
could be written to prefer those tracepoints over using kprobes. As an
example:
====
probe syscall.access = kernel.trace("sys_enter_access") !,
kernel.function("sys_access").call
{
# ... we'd probably need to use @defined() to get the correct arguments
}
====
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug tapsets/14690] the syscall tapsets could be written to prefer the 'syscalls' tracepoints
2012-10-09 19:41 [Bug tapsets/14690] New: the syscall tapsets could be written to prefer the 'syscalls' tracepoints dsmith at redhat dot com
@ 2012-10-09 20:14 ` jistone at redhat dot com
2018-06-20 19:26 ` fche at redhat dot com
2018-10-11 13:31 ` juddin at redhat dot com
2 siblings, 0 replies; 4+ messages in thread
From: jistone at redhat dot com @ 2012-10-09 20:14 UTC (permalink / raw)
To: systemtap
http://sourceware.org/bugzilla/show_bug.cgi?id=14690
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jistone at redhat dot com
--- Comment #1 from Josh Stone <jistone at redhat dot com> 2012-10-09 20:14:12 UTC ---
(In reply to comment #0)
> probe syscall.access = kernel.trace("sys_enter_access") !,
> kernel.function("sys_access").call
> {
> # ... we'd probably need to use @defined() to get the correct arguments
> }
IMO, when we already know what variables should be used in which probe point,
it's better to split the aliases than use @defined, e.g.
probe syscall.access = tp_syscall.access!, kp_syscall.access
{ /* common stuff */ }
probe tp_syscall.access = kernel.trace("sys_enter_access")
{ /* tracepoint specifics */ }
probe kp_syscall.access = kernel.function("sys_access").call
{ /* kprobe specifics */ }
We might even choose to unify nd_syscall.access in there too.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug tapsets/14690] the syscall tapsets could be written to prefer the 'syscalls' tracepoints
2012-10-09 19:41 [Bug tapsets/14690] New: the syscall tapsets could be written to prefer the 'syscalls' tracepoints dsmith at redhat dot com
2012-10-09 20:14 ` [Bug tapsets/14690] " jistone at redhat dot com
@ 2018-06-20 19:26 ` fche at redhat dot com
2018-10-11 13:31 ` juddin at redhat dot com
2 siblings, 0 replies; 4+ messages in thread
From: fche at redhat dot com @ 2018-06-20 19:26 UTC (permalink / raw)
To: systemtap
https://sourceware.org/bugzilla/show_bug.cgi?id=14690
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
This little toy script checks whether the _stp_syscall_nr() function provides a
good-enough substitute for the missing $id parameter from the sys_exit
tracepoint. It turns out that generally yes, at least on x86_64.
global i%
probe kernel.trace("sys_enter") { __set_usermode_pt_regs($regs) x=$id
y=_stp_syscall_nr(); i[tid()]=x; if (x!=y) println("entry ", x, " ", y) }
probe kernel.trace("sys_exit") { __set_usermode_pt_regs($regs) y =
_stp_syscall_nr(); x=i[tid()]; delete i[tid()] ; if(x!=y) println("exit ", x, "
", y) }
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug tapsets/14690] the syscall tapsets could be written to prefer the 'syscalls' tracepoints
2012-10-09 19:41 [Bug tapsets/14690] New: the syscall tapsets could be written to prefer the 'syscalls' tracepoints dsmith at redhat dot com
2012-10-09 20:14 ` [Bug tapsets/14690] " jistone at redhat dot com
2018-06-20 19:26 ` fche at redhat dot com
@ 2018-10-11 13:31 ` juddin at redhat dot com
2 siblings, 0 replies; 4+ messages in thread
From: juddin at redhat dot com @ 2018-10-11 13:31 UTC (permalink / raw)
To: systemtap
https://sourceware.org/bugzilla/show_bug.cgi?id=14690
Jafeer Uddin <juddin at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |juddin at redhat dot com
Resolution|--- |FIXED
Assignee|systemtap at sourceware dot org |juddin at redhat dot com
--- Comment #3 from Jafeer Uddin <juddin at redhat dot com> ---
All syscall tracepoints have been added in commit
8b8c9b636389b67a2288e31eb1f9b14a3992bc18
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-10-11 13:31 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-10-09 19:41 [Bug tapsets/14690] New: the syscall tapsets could be written to prefer the 'syscalls' tracepoints dsmith at redhat dot com
2012-10-09 20:14 ` [Bug tapsets/14690] " jistone at redhat dot com
2018-06-20 19:26 ` fche at redhat dot com
2018-10-11 13:31 ` juddin 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).