Documentation: kprobetrace: document 'trigger' file
As the other files are documented explicitly, let's add a short description for 'trigger' as well. Signed-off-by: Andreas Ziegler <andreas.ziegler@fau.de> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
e50891d6ef
commit
31130c8ec8
|
@ -81,7 +81,7 @@ Per-probe event filtering feature allows you to set different filter on each
|
|||
probe and gives you what arguments will be shown in trace buffer. If an event
|
||||
name is specified right after 'p:' or 'r:' in kprobe_events, it adds an event
|
||||
under tracing/events/kprobes/<EVENT>, at the directory you can see 'id',
|
||||
'enable', 'format' and 'filter'.
|
||||
'enable', 'format', 'filter' and 'trigger'.
|
||||
|
||||
enable:
|
||||
You can enable/disable the probe by writing 1 or 0 on it.
|
||||
|
@ -95,6 +95,9 @@ filter:
|
|||
id:
|
||||
This shows the id of this probe event.
|
||||
|
||||
trigger:
|
||||
This allows to install trigger commands which are executed when the event is
|
||||
hit (for details, see Documentation/trace/events.rst, section 6).
|
||||
|
||||
Event Profiling
|
||||
---------------
|
||||
|
|
Loading…
Reference in New Issue