From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, Michael Petlan <mpetlan@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [PATCH 04/10] perf script: Fix man page about --dump-raw-trace option
Date: Tue, 17 Jan 2017 13:06:59 -0300 [thread overview]
Message-ID: <20170117160705.16055-5-acme@kernel.org> (raw)
In-Reply-To: <20170117160705.16055-1-acme@kernel.org>
From: Michael Petlan <mpetlan@redhat.com>
The "--dump-raw-script" is not a valid option, replace it with the valid
one, "--dump-raw-trace"
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Fixes: 133dc4c39c57 ("perf: Rename 'perf trace' to 'perf script'")
LPU-Reference: 728644547.14560155.1484320012612.JavaMail.zimbra@redhat.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/Documentation/perf-script.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/Documentation/perf-script.txt b/tools/perf/Documentation/perf-script.txt
index 5dc5c6a09ac4..4ed5f239ba7d 100644
--- a/tools/perf/Documentation/perf-script.txt
+++ b/tools/perf/Documentation/perf-script.txt
@@ -36,7 +36,7 @@ There are several variants of perf script:
'perf script report <script> [args]' to run and display the results
of <script>. <script> is the name displayed in the output of 'perf
- trace --list' i.e. the actual script name minus any language
+ script --list' i.e. the actual script name minus any language
extension. The perf.data output from a previous run of 'perf script
record <script>' is used and should be present for this command to
succeed. [args] refers to the (mainly optional) args expected by
@@ -76,7 +76,7 @@ OPTIONS
Any command you can specify in a shell.
-D::
---dump-raw-script=::
+--dump-raw-trace=::
Display verbose dump of the trace data.
-L::
--
2.9.3
next prev parent reply other threads:[~2017-01-17 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 16:06 [GIT PULL 00/10] perf/core improvements and fixes Arnaldo Carvalho de Melo
2017-01-17 16:06 ` [PATCH 01/10] perf pmu: Factor out scale conversion code Arnaldo Carvalho de Melo
2017-01-17 16:06 ` [PATCH 02/10] perf tools: Remove unneccessary feature-dwarf warning Arnaldo Carvalho de Melo
2017-01-17 16:06 ` [PATCH 03/10] tools lib subcmd: Fix missing member name Arnaldo Carvalho de Melo
2017-01-17 16:06 ` Arnaldo Carvalho de Melo [this message]
2017-01-17 16:07 ` [PATCH 05/10] perf script: Also allow forcing reading of non-root owned files by root Arnaldo Carvalho de Melo
2017-01-17 16:07 ` [PATCH 06/10] perf sched timehist: Account thread wait time separately Arnaldo Carvalho de Melo
2017-01-17 16:07 ` [PATCH 07/10] perf sched timehist: Add --state option Arnaldo Carvalho de Melo
2017-01-17 16:07 ` [PATCH 08/10] perf sched timehist: Show total wait times for summary Arnaldo Carvalho de Melo
2017-01-17 16:07 ` [PATCH 09/10] perf tools: Move two variables usied in libperf from perf.c Arnaldo Carvalho de Melo
2017-01-17 16:07 ` [PATCH 10/10] perf evlist: Fix typo in deliver_sample() Arnaldo Carvalho de Melo
2017-01-18 9:09 ` [GIT PULL 00/10] perf/core improvements and fixes Ingo Molnar
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=20170117160705.16055-5-acme@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=tglx@linutronix.de \
/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).