From 954eb3bf2ec00f54511c1de06bac8077898a86f6 Mon Sep 17 00:00:00 2001 From: Philippe Proulx Date: Mon, 28 Nov 2016 18:54:41 -0500 Subject: [PATCH] lttng-add-context(1): fix style MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Signed-off-by: Philippe Proulx Signed-off-by: Jérémie Galarneau --- doc/man/lttng-add-context.1.txt | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/doc/man/lttng-add-context.1.txt b/doc/man/lttng-add-context.1.txt index fe2412e30..9027f8309 100644 --- a/doc/man/lttng-add-context.1.txt +++ b/doc/man/lttng-add-context.1.txt @@ -46,13 +46,17 @@ can only be used in the Linux kernel tracing domain, while per-thread counters can only be used in the user space tracing domain. It is also possible to enable PMU counters by raw ID using the -`perf:cpu:raw:r:` or `perf:thread:raw:r:` format for -the kernel and user-space respectively. `` is a hexadecimal event -descriptor which is the same format as used by perf-record(1): a -concatenation of the `Umask value` and `Event number` provided by the -processor's manufacturer. The possible values for this field are -processor-specific. The `` field is used to associate a clearer -name to the counter. +`perf:cpu:raw:rN:NAME` (Linux kernel tracing domain) or +`perf:thread:raw:rN:NAME` (user space tracing domain), with: + +`N`:: + A hexadecimal event descriptor which is the same format as used + by 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. + +`NAME`:: + Custom name to easily recognize the counter. Application-specific context fields can be added to a channel using the following syntax: -- 2.34.1