From 31130c8ec8cc03dec563b8e1317be508d4268225 Mon Sep 17 00:00:00 2001 From: Andreas Ziegler Date: Mon, 16 Jul 2018 13:05:58 +0200 Subject: 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 Signed-off-by: Jonathan Corbet --- Documentation/trace/kprobetrace.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'Documentation/trace') diff --git a/Documentation/trace/kprobetrace.rst b/Documentation/trace/kprobetrace.rst index c4aaef7d7c89..8bfc75c90806 100644 --- a/Documentation/trace/kprobetrace.rst +++ b/Documentation/trace/kprobetrace.rst @@ -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/, 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 --------------- -- cgit v1.2.3