lttng-disable-event(1): `--tracepoint` option is not the default

I previously thought that not specifying any instrumentation point type
option was equivalent to specifying `--tracepoint`, like with the
`enable-event` command.

It's not the case: `--tracepoint` is just a filter, like `--syscall` and
the others. With `--kernel`, if you don't specify any instrumentation
point type condition option, the `disable-event` command disables
recording event rules regardless of their instrumentation point type.

This patch updates lttng-disable-event(1) to explain this.

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Change-Id: I489c5d16dae954f4b5116edce556fdd942c98c4d

diff --git a/doc/man/lttng-disable-event.1.txt b/doc/man/lttng-disable-event.1.txt
index 2f09d3873c71a591ec5879ba5a27daa1e38c86ef..1fdeba1988c76e7c16fb599c1c79cc92f48b3531 100644 (file)
--- a/doc/man/lttng-disable-event.1.txt
+++ b/doc/man/lttng-disable-event.1.txt
@@ -56,6 +56,11 @@ type and event name conditions. Therefore, you cannot disable recording
 event rules having a specific instrumentation point log level condition,
 for example.
 
+With the option:--kernel option and no instrumentation point type
+condition option, the `disable-event` command disables one or more Linux
+kernel recording event rules regardless of their instrumentation point
+type.
+
 List the recording event rules of a given tracing session
 and/or channel with the man:lttng-list(1) command.
 
@@ -135,9 +140,6 @@ With the option:--kernel or option:--userspace option:::
 With the option:--jul, option:--log4j, or option:--python option:::
     Logging events.
 --
-+
-As of LTTng{nbsp}{lttng_version}, this is the default instrumentation
-point type condition option, but this may change in the future.
 
 
 Event name condition