This is the mail archive of the systemtap@sourceware.org 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/16540] New: the scsi tapset could use the scsi tracepoints


https://sourceware.org/bugzilla/show_bug.cgi?id=16540

            Bug ID: 16540
           Summary: the scsi tapset could use the scsi tracepoints
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: tapsets
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com

In newer kernels, scsi tracepoints have been added:

# stap -L 'kernel.trace("*scsi*")'
kernel.trace("scsi_dispatch_cmd_done") $cmd:struct scsi_cmnd*
kernel.trace("scsi_dispatch_cmd_error") $cmd:struct scsi_cmnd* $rtn:int
kernel.trace("scsi_dispatch_cmd_start") $cmd:struct scsi_cmnd*
kernel.trace("scsi_dispatch_cmd_timeout") $cmd:struct scsi_cmnd*
kernel.trace("scsi_eh_wakeup") $shost:struct Scsi_Host*

Support for these tracepoints could be added to the scsi tapset. For instance,
the 'scsi_dispatch_cmd_done' tracepoint is called as the first thing in the
scsi_done() function, which means the scsi.iodone probe alias could be written
to prefer the tracepoint to a function probe.

-- 
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]