This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/13330] New: Support TRACE_SYSTEM for tracepoints
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Fri, 21 Oct 2011 20:03:03 +0000
- Subject: [Bug tapsets/13330] New: Support TRACE_SYSTEM for tracepoints
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13330
Bug #: 13330
Summary: Support TRACE_SYSTEM for tracepoints
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: tapsets
AssignedTo: systemtap@sourceware.org
ReportedBy: jistone@redhat.com
Classification: Unclassified
Kernel tracepoints have a TRACE_SYSTEM which describes a sort of namespace for
the probe points. e.g. skb, net, napi, scsi:
$ perf list tracepoint | head
skb:kfree_skb [Tracepoint event]
skb:consume_skb [Tracepoint event]
skb:skb_copy_datagram_iovec [Tracepoint event]
net:net_dev_xmit [Tracepoint event]
net:net_dev_queue [Tracepoint event]
net:netif_receive_skb [Tracepoint event]
net:netif_rx [Tracepoint event]
napi:napi_poll [Tracepoint event]
scsi:scsi_dispatch_cmd_start [Tracepoint event]
scsi:scsi_dispatch_cmd_error [Tracepoint event]
We could add support for this in a couple of ways. One is to make a new
context string, perhaps $$system. We could also introduce this into the probe
syntax for selecting tracepoints.
current syntax: kernel.trace("NAME")
new syntax: kernel.trace("SYSTEM:NAME")
or perhaps: kernel.system("SYSTEM").trace("NAME")
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.