From: Adrian Hunter <adrian.hun...@intel.com>

perf script, report and inject all have the same itrace options. Put
them into an asciidoc include file.

Signed-off-by: Adrian Hunter <adrian.hun...@intel.com>
Cc: Jiri Olsa <jo...@redhat.com>
Link: 
http://lkml.kernel.org/r/1437150840-31811-10-git-send-email-adrian.hun...@intel.com
Signed-off-by: Arnaldo Carvalho de Melo <a...@redhat.com>
---
 tools/perf/Documentation/itrace.txt      | 22 ++++++++++++++++++++++
 tools/perf/Documentation/perf-inject.txt | 23 +----------------------
 tools/perf/Documentation/perf-report.txt | 23 +----------------------
 tools/perf/Documentation/perf-script.txt | 23 +----------------------
 4 files changed, 25 insertions(+), 66 deletions(-)
 create mode 100644 tools/perf/Documentation/itrace.txt

diff --git a/tools/perf/Documentation/itrace.txt 
b/tools/perf/Documentation/itrace.txt
new file mode 100644
index 000000000000..2ff946677e3b
--- /dev/null
+++ b/tools/perf/Documentation/itrace.txt
@@ -0,0 +1,22 @@
+               i       synthesize instructions events
+               b       synthesize branches events
+               c       synthesize branches events (calls only)
+               r       synthesize branches events (returns only)
+               x       synthesize transactions events
+               e       synthesize error events
+               d       create a debug log
+               g       synthesize a call chain (use with i or x)
+
+       The default is all events i.e. the same as --itrace=ibxe
+
+       In addition, the period (default 100000) for instructions events
+       can be specified in units of:
+
+               i       instructions
+               t       ticks
+               ms      milliseconds
+               us      microseconds
+               ns      nanoseconds (default)
+
+       Also the call chain size (default 16, max. 1024) for instructions or
+       transactions events can be specified.
diff --git a/tools/perf/Documentation/perf-inject.txt 
b/tools/perf/Documentation/perf-inject.txt
index b876ae312699..0c721c3e37e1 100644
--- a/tools/perf/Documentation/perf-inject.txt
+++ b/tools/perf/Documentation/perf-inject.txt
@@ -48,28 +48,7 @@ OPTIONS
        Decode Instruction Tracing data, replacing it with synthesized events.
        Options are:
 
-               i       synthesize instructions events
-               b       synthesize branches events
-               c       synthesize branches events (calls only)
-               r       synthesize branches events (returns only)
-               x       synthesize transactions events
-               e       synthesize error events
-               d       create a debug log
-               g       synthesize a call chain (use with i or x)
-
-       The default is all events i.e. the same as --itrace=ibxe
-
-       In addition, the period (default 100000) for instructions events
-       can be specified in units of:
-
-               i       instructions
-               t       ticks
-               ms      milliseconds
-               us      microseconds
-               ns      nanoseconds (default)
-
-       Also the call chain size (default 16, max. 1024) for instructions or
-       transactions events can be specified.
+include::itrace.txt[]
 
 SEE ALSO
 --------
diff --git a/tools/perf/Documentation/perf-report.txt 
b/tools/perf/Documentation/perf-report.txt
index a18ba757a0ed..9c7981bfddad 100644
--- a/tools/perf/Documentation/perf-report.txt
+++ b/tools/perf/Documentation/perf-report.txt
@@ -331,28 +331,7 @@ OPTIONS
 --itrace::
        Options for decoding instruction tracing data. The options are:
 
-               i       synthesize instructions events
-               b       synthesize branches events
-               c       synthesize branches events (calls only)
-               r       synthesize branches events (returns only)
-               x       synthesize transactions events
-               e       synthesize error events
-               d       create a debug log
-               g       synthesize a call chain (use with i or x)
-
-       The default is all events i.e. the same as --itrace=ibxe
-
-       In addition, the period (default 100000) for instructions events
-       can be specified in units of:
-
-               i       instructions
-               t       ticks
-               ms      milliseconds
-               us      microseconds
-               ns      nanoseconds (default)
-
-       Also the call chain size (default 16, max. 1024) for instructions or
-       transactions events can be specified.
+include::itrace.txt[]
 
        To disable decoding entirely, use --no-itrace.
 
diff --git a/tools/perf/Documentation/perf-script.txt 
b/tools/perf/Documentation/perf-script.txt
index 8e9be1f9c1dd..c0d24791a7f3 100644
--- a/tools/perf/Documentation/perf-script.txt
+++ b/tools/perf/Documentation/perf-script.txt
@@ -235,28 +235,7 @@ OPTIONS
 --itrace::
        Options for decoding instruction tracing data. The options are:
 
-               i       synthesize instructions events
-               b       synthesize branches events
-               c       synthesize branches events (calls only)
-               r       synthesize branches events (returns only)
-               x       synthesize transactions events
-               e       synthesize error events
-               d       create a debug log
-               g       synthesize a call chain (use with i or x)
-
-       The default is all events i.e. the same as --itrace=ibxe
-
-       In addition, the period (default 100000) for instructions events
-       can be specified in units of:
-
-               i       instructions
-               t       ticks
-               ms      milliseconds
-               us      microseconds
-               ns      nanoseconds (default)
-
-       Also the call chain size (default 16, max. 1024) for instructions or
-       transactions events can be specified.
+include::itrace.txt[]
 
        To disable decoding entirely, use --no-itrace.
 
-- 
2.1.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to