summaryrefslogtreecommitdiffstats
path: root/CREDITS
diff options
context:
space:
mode:
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>2014-01-07 10:31:04 -0500
committerSteven Rostedt <rostedt@goodmis.org>2014-01-09 21:20:32 -0500
commitdd97b95438c812d8fd93d9426661a6c8e1520005 (patch)
tree1fa83336880595da7dc881fde5aab453d17e12ab /CREDITS
parent13a1e4aef53b2a7684ddee374e749999ba103b4a (diff)
downloadop-kernel-dev-dd97b95438c812d8fd93d9426661a6c8e1520005.zip
op-kernel-dev-dd97b95438c812d8fd93d9426661a6c8e1520005.tar.gz
tracing: Show available event triggers when no trigger is set
Currently there's no way to know what triggers exist on a kernel without looking at the source of the kernel or randomly trying out triggers. Instead of creating another file in the debugfs system, simply show what available triggers are there when cat'ing the trigger file when it has no events: [root /sys/kernel/debug/tracing]# cat events/sched/sched_switch/trigger # Available triggers: # traceon traceoff snapshot stacktrace enable_event disable_event This stays consistent with other debugfs files where meta data like this is always proceeded with a '#' at the start of the line so that tools can strip these out. Link: http://lkml.kernel.org/r/20140107103548.0a84536d@gandalf.local.home Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud