Added description of "trace-cmd report --cpu ..." option in
"trace-cmd report --help" output and in "trace-cmd report" man page.
Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@xxxxxxxxx>
---
Documentation/trace-cmd-report.1.txt | 9 +++++++++
tracecmd/trace-usage.c | 2 ++
2 files changed, 11 insertions(+)
diff --git a/Documentation/trace-cmd-report.1.txt b/Documentation/trace-cmd-report.1.txt
index 66e96da7..864eb2d7 100644
--- a/Documentation/trace-cmd-report.1.txt
+++ b/Documentation/trace-cmd-report.1.txt
@@ -242,6 +242,15 @@ OPTIONS
Example: -O fgraph:tailprint
+*--cpu* <cpu list>::
+ List of CPUs, separated by "," or ":", used for filtering the events.
+ A range of CPUs can be specified using "cpuX-cpuY" notation, where all CPUs
+ in the range between cpuX and cpuY will be included in the list. The order
+ of CPUs in the list must be from lower to greater.
+
+ Example: "--cpu 0,3" - show events from CPUs 0 and 3
+ "--cpu 2-4" - show events from CPUs 2, 3 and 4
+
*--stat*::
If the trace.dat file recorded the final stats (outputed at the end of record)
the *--stat* option can be used to retrieve them.
diff --git a/tracecmd/trace-usage.c b/tracecmd/trace-usage.c
index 85c63512..3f0b2d07 100644
--- a/tracecmd/trace-usage.c
+++ b/tracecmd/trace-usage.c
@@ -209,6 +209,8 @@ static struct usage_help usage_help[] = {
" -w show wakeup latencies\n"
" -l show latency format (default with latency tracers)\n"
" -O plugin option -O [plugin:]var[=val]\n"
+ " --cpu <cpu1,cpu2,...> - filter events according to the given cpu list.\n"
+ " A range of CPUs can be specified using 'cpuX-cpuY' notation.\n"
" --check-events return whether all event formats can be parsed\n"
" --stat - show the buffer stats that were reported at the end of the record.\n"
" --uname - show uname of the record, if it was saved\n"
--
2.26.2
|