From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Nambong Ha <over3025@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Taeung Song <taeung@kosslab.kr>
Subject: Re: [PATCH] perf config: Add tips about a list option
Date: Thu, 29 Sep 2016 19:28:48 -0300 [thread overview]
Message-ID: <20160929222848.GC29214@kernel.org> (raw)
In-Reply-To: <1475184468-5145-1-git-send-email-over3025@gmail.com>
Em Fri, Sep 30, 2016 at 06:27:48AM +0900, Nambong Ha escreveu:
> Add two tips that describe --list option of config sub-command
> and explain how to choose particular config file location.
>
> Signed-off-by: Nambong Ha <over3025@gmail.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Taeung Song <taeung@kosslab.kr>
> ---
> tools/perf/Documentation/tips.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/perf/Documentation/tips.txt b/tools/perf/Documentation/tips.txt
> index 5950b5a..1929654 100644
> --- a/tools/perf/Documentation/tips.txt
> +++ b/tools/perf/Documentation/tips.txt
> @@ -28,3 +28,5 @@ To change sampling frequency to 100 Hz: perf record -F 100
> See assembly instructions with percentage: perf annotate <symbol>
> If you prefer Intel style assembly, try: perf annotate -M intel
> For hierarchical output, try: perf report --hierarchy
> +Show current config key-value pairs: perf config --list
> +If choosing particular config file location, e.g.: perf config --user -l
Humm, the second seems to use the context of the first, but these will
be chosen randomly, so the second needs to be rewritten to something
like:
Show user configuration overrides: perf config --user --list
No?
- Arnaldo
prev parent reply other threads:[~2016-09-29 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 21:27 [PATCH] perf config: Add tips about a list option Nambong Ha
2016-09-29 22:28 ` 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=20160929222848.GC29214@kernel.org \
--to=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=over3025@gmail.com \
--cc=peterz@infradead.org \
--cc=taeung@kosslab.kr \
/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