From e50891d6eff5bc446ecf5d4c04906a19d2eb8424 Mon Sep 17 00:00:00 2001 From: Andreas Ziegler Date: Mon, 16 Jul 2018 13:05:57 +0200 Subject: Documentation: {u,k}probes: fix filename for event enabling The per-event files to enable or disable kprobes and uprobes are named 'enable', not 'enabled'. Fix the corresponding documentation. Signed-off-by: Andreas Ziegler Signed-off-by: Jonathan Corbet --- Documentation/trace/kprobetrace.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'Documentation/trace/kprobetrace.rst') diff --git a/Documentation/trace/kprobetrace.rst b/Documentation/trace/kprobetrace.rst index 3e0f971b12de..c4aaef7d7c89 100644 --- a/Documentation/trace/kprobetrace.rst +++ b/Documentation/trace/kprobetrace.rst @@ -18,7 +18,7 @@ To enable this feature, build your kernel with CONFIG_KPROBE_EVENTS=y. Similar to the events tracer, this doesn't need to be activated via current_tracer. Instead of that, add probe points via /sys/kernel/debug/tracing/kprobe_events, and enable it via -/sys/kernel/debug/tracing/events/kprobes//enabled. +/sys/kernel/debug/tracing/events/kprobes//enable. Synopsis of kprobe_events @@ -81,9 +81,9 @@ 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', -'enabled', 'format' and 'filter'. +'enable', 'format' and 'filter'. -enabled: +enable: You can enable/disable the probe by writing 1 or 0 on it. format: -- cgit v1.2.3-59-g8ed1b