diff options
| author | Roman Bolshakov <[email protected]> | 2020-09-29 15:59:57 +0300 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2020-10-02 18:36:19 -0400 |
| commit | 7010645ba7256992818b518163f46bd4cdf8002a (patch) | |
| tree | 1aa8b7c6edb70f55248c075d2191fdb265763c6a /tools/perf/scripts/python | |
| parent | 718c2fe92b208415fa76550975dc5d7708448f7c (diff) | |
scsi: target: core: Add CONTROL field for trace events
trace-cmd report doesn't show events from target subsystem because
scsi_command_size() leaks through event format string:
[target:target_sequencer_start] function scsi_command_size not defined
[target:target_cmd_complete] function scsi_command_size not defined
Addition of scsi_command_size() to plugin_scsi.c in trace-cmd doesn't
help because an expression is used inside TP_printk(). trace-cmd event
parser doesn't understand minus sign inside [ ]:
Error: expected ']' but read '-'
Rather than duplicating kernel code in plugin_scsi.c, provide a dedicated
field for CONTROL byte.
Link: https://lore.kernel.org/r/[email protected]
Reviewed-by: Mike Christie <[email protected]>
Signed-off-by: Roman Bolshakov <[email protected]>
Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions