common: move copy_filter_bytecode to bytecode.c and rename it

[lttng-tools.git] / doc / man / lttng-add-context.1.txt

diff --git a/doc/man/lttng-add-context.1.txt b/doc/man/lttng-add-context.1.txt
index 9027f8309db29c8f9dfcba81acb706c78936bced..640da1db1309dda5c81c466dc78a994e01cacc41 100644 (file)
--- a/doc/man/lttng-add-context.1.txt
+++ b/doc/man/lttng-add-context.1.txt
@@ -1,5 +1,6 @@
 lttng-add-context(1)
 ====================
+:revdate: 5 Februrary 2018
 
 
 NAME
@@ -51,7 +52,7 @@ It is also possible to enable PMU counters by raw ID using the
 
 `N`::
     A hexadecimal event descriptor which is the same format as used
-    by perf-record(1): a concatenation of the event number and umask
+    by man:perf-record(1): a concatenation of the event number and umask
     value provided by the processor's manufacturer. The possible values
     for this field are processor-specific.
 
@@ -79,6 +80,8 @@ most shells.
 Use the option:--list option without other arguments to list the
 available context field names.
 
+See the <<limitations,LIMITATIONS>> section below for a list of
+limitations to consider.
 
 include::common-cmd-options-head.txt[]
 
@@ -123,6 +126,12 @@ option:-t 'TYPE', option:--type='TYPE'::
 
 include::common-cmd-help-options.txt[]
 
+[[limitations]]
+LIMITATIONS
+-----------
+As of this version of LTTng, it is not possible to add context fields to
+a channel once its tracing session has been started (see man:lttng-start(1))
+at least once.
 
 include::common-cmd-footer.txt[]