From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Milian Wolff <milian.wolff@kdab.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 2/2] perf config: Show default report configuration in example and docs
Date: Wed, 31 Aug 2016 18:49:41 -0300 [thread overview]
Message-ID: <20160831214941.GC13095@kernel.org> (raw)
In-Reply-To: <20160830134106.21240-2-milian.wolff@kdab.com>
Em Tue, Aug 30, 2016 at 03:41:06PM +0200, Milian Wolff escreveu:
> Signed-off-by: Milian Wolff <milian.wolff@kdab.com>
Thanks, applied to perf/core.
- Arnaldo
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> ---
> tools/perf/Documentation/perf-config.txt | 8 ++++++++
> tools/perf/Documentation/perfconfig.example | 9 +++++++++
> 2 files changed, 17 insertions(+)
>
> diff --git a/tools/perf/Documentation/perf-config.txt b/tools/perf/Documentation/perf-config.txt
> index c7031bc..1559000 100644
> --- a/tools/perf/Documentation/perf-config.txt
> +++ b/tools/perf/Documentation/perf-config.txt
> @@ -110,6 +110,14 @@ Given a $HOME/.perfconfig like this:
> order = caller
> sort-key = function
>
> + [report]
> + # Defaults
> + sort-order = comm,dso,symbol
> + percent-limit = 0
> + queue-size = 0
> + children = true
> + group = true
> +
> Variables
> ~~~~~~~~~
>
> diff --git a/tools/perf/Documentation/perfconfig.example b/tools/perf/Documentation/perfconfig.example
> index 1d8d5bc..2b477c1 100644
> --- a/tools/perf/Documentation/perfconfig.example
> +++ b/tools/perf/Documentation/perfconfig.example
> @@ -27,3 +27,12 @@
> use_offset = true
> jump_arrows = true
> show_nr_jumps = false
> +
> +[report]
> +
> + # Defaults
> + sort-order = comm,dso,symbol
> + percent-limit = 0
> + queue-size = 0
> + children = true
> + group = true
> --
> 2.9.3
prev parent reply other threads:[~2016-08-31 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 13:41 [PATCH 1/2] perf report: Accept report.sort-order as synonym to report.sort_order Milian Wolff
2016-08-30 13:41 ` [PATCH 2/2] perf config: Show default report configuration in example and docs Milian Wolff
2016-08-31 21:49 ` 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=20160831214941.GC13095@kernel.org \
--to=acme@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.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;
as well as URLs for NNTP newsgroup(s).