summaryrefslogtreecommitdiffstats
path: root/kernel/trace/trace.h
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@linux.intel.com>2013-10-24 08:59:27 -0500
committerSteven Rostedt <rostedt@goodmis.org>2013-12-21 22:02:15 -0500
commitf21ecbb35f865a508073c0e73854da469a07f278 (patch)
tree75f014738b5bbe844abdf087b6897b14c6c29bd9 /kernel/trace/trace.h
parent93e31ffbf417a84fbae518fb46b3ea3f0d8fa6e1 (diff)
downloadop-kernel-dev-f21ecbb35f865a508073c0e73854da469a07f278.zip
op-kernel-dev-f21ecbb35f865a508073c0e73854da469a07f278.tar.gz
tracing: Add 'stacktrace' event trigger command
Add 'stacktrace' event_command. stacktrace event triggers are added by the user via this command in a similar way and using practically the same syntax as the analogous 'stacktrace' ftrace function command, but instead of writing to the set_ftrace_filter file, the stacktrace event trigger is written to the per-event 'trigger' files: echo 'stacktrace' > .../tracing/events/somesys/someevent/trigger The above command will turn on stacktraces for someevent i.e. whenever someevent is hit, a stacktrace will be logged. This also adds a 'count' version that limits the number of times the command will be invoked: echo 'stacktrace:N' > .../tracing/events/somesys/someevent/trigger Where N is the number of times the command will be invoked. The above command will log N stacktraces for someevent i.e. whenever someevent is hit N times, a stacktrace will be logged. Link: http://lkml.kernel.org/r/0c30c008a0828c660aa0e1bbd3255cf179ed5c30.1382622043.git.tom.zanussi@linux.intel.com Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/trace.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud