Lines Matching refs:trigger

294 Trace events can be made to conditionally invoke trigger 'commands'
298 with attached triggers is invoked, the set of trigger commands
299 associated with that event is invoked.  Any given trigger can
303 If no filter is associated with the trigger, it always passes.
306 trigger expressions to the 'trigger' file for the given event.
330 Triggers are added by echoing the command to the 'trigger' file:
332   # echo 'command[:count] [if filter]' > trigger
335 to the 'trigger' file:
337   # echo '!command[:count] [if filter]' > trigger
346 For ease of use, writing to the trigger file using '>' currently just
347 adds or removes a single trigger and there's no explicit '>>' support
351 6.2 Supported trigger commands
362   The event tracepoint stays in this mode as long as there's a trigger
363   in effect that can trigger it.
365   For example, the following trigger causes kmalloc events to be
370       /sys/kernel/debug/tracing/events/syscalls/sys_enter_read/trigger
372   The following trigger causes kmalloc events to stop being traced
377       /sys/kernel/debug/tracing/events/syscalls/sys_exit_read/trigger
387       /sys/kernel/debug/tracing/events/syscalls/sys_enter_read/trigger
390       /sys/kernel/debug/tracing/events/syscalls/sys_exit_read/trigger
393   per triggering event, but there can only be one trigger per
405   For example, the following trigger dumps a stacktrace every time the
409         /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
411   The following trigger dumps a stacktrace the first 5 times a kmalloc
415         /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
424         /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
427         /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
433         /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
435   Note that there can be only one stacktrace trigger per triggering
446   capture those events when the trigger event occurred:
449         /sys/kernel/debug/tracing/events/block/block_unplug/trigger
454         /sys/kernel/debug/tracing/events/block/block_unplug/trigger
459         /sys/kernel/debug/tracing/events/block/block_unplug/trigger
462         /sys/kernel/debug/tracing/events/block/block_unplug/trigger
464   Note that there can be only one snapshot trigger per triggering
477   trigger event:
480         /sys/kernel/debug/tracing/events/block/block_unplug/trigger
485         /sys/kernel/debug/tracing/events/block/block_unplug/trigger
490         /sys/kernel/debug/tracing/events/block/block_unplug/trigger
493         /sys/kernel/debug/tracing/events/block/block_unplug/trigger
495   Note that there can be only one traceon or traceoff trigger per