From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Zejiang Tang <tangzejiang@loongson.cn>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>,
Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] Improve perf option help information in perf.txt
Date: Thu, 17 Sep 2020 16:04:41 -0300 [thread overview]
Message-ID: <20200917190441.GC1426933@kernel.org> (raw)
In-Reply-To: <CAM9d7cignBfmuNB9hkKFW4Zsm7LT86zX54VEyQPuDGdkdQv-tQ@mail.gmail.com>
Em Wed, Sep 09, 2020 at 10:03:34PM +0900, Namhyung Kim escreveu:
> On Wed, Sep 9, 2020 at 6:53 PM Zejiang Tang <tangzejiang@loongson.cn> wrote:
> >
> > Perf could use many options, such as:-vv, --exec-path,
> > --html-path, -p, --paginate,--no-pager, --debugfs-dir,
> > --buildid-dir, --list-cmds, --list-opts. Add these options
> > in perf.txt.
> >
> > Signed-off-by: Zejiang Tang <tangzejiang@loongson.cn>
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks, applied.
- Arnaldo
> Thanks
> Namhyung
>
>
> > ---
> > tools/perf/Documentation/perf.txt | 69 ++++++++++++++++++++++++++-------------
> > 1 file changed, 47 insertions(+), 22 deletions(-)
> >
> > diff --git a/tools/perf/Documentation/perf.txt b/tools/perf/Documentation/perf.txt
> > index 3f37ded..c130a3c 100644
> > --- a/tools/perf/Documentation/perf.txt
> > +++ b/tools/perf/Documentation/perf.txt
> > @@ -12,32 +12,57 @@ SYNOPSIS
> >
> > OPTIONS
> > -------
> > ---debug::
> > - Setup debug variable (see list below) in value
> > - range (0, 10). Use like:
> > - --debug verbose # sets verbose = 1
> > - --debug verbose=2 # sets verbose = 2
> > -
> > - List of debug variables allowed to set:
> > - verbose - general debug messages
> > - ordered-events - ordered events object debug messages
> > - data-convert - data convert command debug messages
> > - stderr - write debug output (option -v) to stderr
> > - in browser mode
> > - perf-event-open - Print perf_event_open() arguments and
> > - return value
> > -
> > ---buildid-dir::
> > - Setup buildid cache directory. It has higher priority than
> > - buildid.dir config file option.
> > +-h::
> > +--help::
> > + Run perf help command.
> >
> > -v::
> > --version::
> > - Display perf version.
> > + Display perf version.
> >
> > --h::
> > ---help::
> > - Run perf help command.
> > +-vv::
> > + Print the compiled-in status of libraries.
> > +
> > +--exec-path::
> > + Display or set exec path.
> > +
> > +--html-path::
> > + Display html documentation path.
> > +
> > +-p::
> > +--paginate::
> > + Set up pager.
> > +
> > +--no-pager::
> > + Do not set pager.
> > +
> > +--buildid-dir::
> > + Setup buildid cache directory. It has higher priority
> > + than buildid.dir config file option.
> > +
> > +--list-cmds::
> > + List the most commonly used perf commands.
> > +
> > +--list-opts::
> > + List available perf options.
> > +
> > +--debugfs-dir::
> > + Set debugfs directory or set environment variable PERF_DEBUGFS_DIR.
> > +
> > +--debug::
> > + Setup debug variable (see list below) in value
> > + range (0, 10). Use like:
> > + --debug verbose # sets verbose = 1
> > + --debug verbose=2 # sets verbose = 2
> > +
> > + List of debug variables allowed to set:
> > + verbose - general debug messages
> > + ordered-events - ordered events object debug messages
> > + data-convert - data convert command debug messages
> > + stderr - write debug output (option -v) to stderr
> > + in browser mode
> > + perf-event-open - Print perf_event_open() arguments and
> > + return value
> >
> > DESCRIPTION
> > -----------
> > --
> > 2.1.0
> >
--
- Arnaldo
prev parent reply other threads:[~2020-09-17 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 9:53 [PATCH v3] Improve perf option help information in perf.txt Zejiang Tang
2020-09-09 13:03 ` Namhyung Kim
2020-09-17 19:04 ` Arnaldo Carvalho de Melo [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=20200917190441.GC1426933@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=tangzejiang@loongson.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.