This is the mail archive of the mailing list for the systemtap project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tapsets/13330] New: Support TRACE_SYSTEM for tracepoints

             Bug #: 13330
           Summary: Support TRACE_SYSTEM for tracepoints
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: tapsets
    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:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]