From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 2/2] trace-cmd: Document "trace-cmd report --cpu ..." option
Date: Fri, 17 Jul 2020 10:57:41 +0300 [thread overview]
Message-ID: <20200717075741.74775-3-tz.stoyanov@gmail.com> (raw)
In-Reply-To: <20200717075741.74775-1-tz.stoyanov@gmail.com>
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@gmail.com>
---
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
prev parent reply other threads:[~2020-07-17 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 7:57 [PATCH 0/2] trace-cmd documentation updates Tzvetomir Stoyanov (VMware)
2020-07-17 7:57 ` [PATCH 1/2] trace-cmd: Man page of trace-cmd clear subcommand Tzvetomir Stoyanov (VMware)
2020-07-17 7:57 ` Tzvetomir Stoyanov (VMware) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200717075741.74775-3-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).