From: tip-bot for Sihyeon Jang <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: acme@redhat.com, linux-kernel@vger.kernel.org, mingo@kernel.org,
hpa@zytor.com, uneedsihyeon@gmail.com, tglx@linutronix.de,
namhyung@kernel.org, jolsa@kernel.org
Subject: [tip:perf/core] perf trace: Document missing option, colons
Date: Sat, 18 Nov 2017 00:37:46 -0800 [thread overview]
Message-ID: <tip-9b9d28a0087608052b39e7d9ee2f07b4e0fd6dca@git.kernel.org> (raw)
In-Reply-To: <1510842367-11011-2-git-send-email-uneedsihyeon@gmail.com>
Commit-ID: 9b9d28a0087608052b39e7d9ee2f07b4e0fd6dca
Gitweb: https://git.kernel.org/tip/9b9d28a0087608052b39e7d9ee2f07b4e0fd6dca
Author: Sihyeon Jang <uneedsihyeon@gmail.com>
AuthorDate: Thu, 16 Nov 2017 23:26:03 +0900
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Thu, 16 Nov 2017 14:50:05 -0300
perf trace: Document missing option, colons
Add missing --force option to the man page.
Signed-off-by: Sihyeon Jang <uneedsihyeon@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Link: http://lkml.kernel.org/r/1510842367-11011-2-git-send-email-uneedsihyeon@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/Documentation/perf-trace.txt | 16 ++++++++++------
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/tools/perf/Documentation/perf-trace.txt b/tools/perf/Documentation/perf-trace.txt
index d53bea6..6909cf1 100644
--- a/tools/perf/Documentation/perf-trace.txt
+++ b/tools/perf/Documentation/perf-trace.txt
@@ -86,18 +86,18 @@ comma-separated list with no space: 0,1. Ranges of CPUs are specified with -: 0-
In per-thread mode with inheritance mode on (default), Events are captured only when
the thread executes on the designated CPUs. Default is to monitor all CPUs.
---duration:
+--duration::
Show only events that had a duration greater than N.M ms.
---sched:
+--sched::
Accrue thread runtime and provide a summary at the end of the session.
--i
---input
+-i::
+--input::
Process events from a given perf data file.
--T
---time
+-T::
+--time::
Print full timestamp rather time relative to first sample.
--comm::
@@ -117,6 +117,10 @@ the thread executes on the designated CPUs. Default is to monitor all CPUs.
Show tool stats such as number of times fd->pathname was discovered thru
hooking the open syscall return + vfs_getname or via reading /proc/pid/fd, etc.
+-f::
+--force::
+ Don't complain, do it.
+
-F=[all|min|maj]::
--pf=[all|min|maj]::
Trace pagefaults. Optionally, you can specify whether you want minor,
next prev parent reply other threads:[~2017-11-18 8:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 14:26 [PATCH 1/6] perf inject: Document missing options Sihyeon Jang
2017-11-16 14:26 ` [PATCH 2/6] perf trace: Document missing option, colons Sihyeon Jang
2017-11-18 8:37 ` tip-bot for Sihyeon Jang [this message]
2017-11-16 14:26 ` [PATCH 3/6] perf timechart: Document missing option Sihyeon Jang
2017-11-18 8:38 ` [tip:perf/core] perf timechart: Document missing --force option tip-bot for Sihyeon Jang
2017-11-16 14:26 ` [PATCH 4/6] perf sched: Document missing option Sihyeon Jang
2017-11-18 8:38 ` [tip:perf/core] perf sched: Document missing --force option tip-bot for Sihyeon Jang
2017-11-16 14:26 ` [PATCH 5/6] perf evlist: Document missing option Sihyeon Jang
2017-11-18 8:38 ` [tip:perf/core] perf evlist: Document missing --force option tip-bot for Sihyeon Jang
2017-11-16 14:26 ` [PATCH 6/6] perf buildid-cache: Document missing option Sihyeon Jang
2017-11-18 8:39 ` [tip:perf/core] perf buildid-cache: Document missing --force option tip-bot for Sihyeon Jang
2017-11-16 14:35 ` [PATCH 1/6] perf inject: Document missing options Arnaldo Carvalho de Melo
2017-11-18 8:37 ` [tip:perf/core] " tip-bot for Sihyeon Jang
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=tip-9b9d28a0087608052b39e7d9ee2f07b4e0fd6dca@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@redhat.com \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--cc=uneedsihyeon@gmail.com \
/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