From: Ingo Molnar <mingo@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf tools: Prevent condition that all sort keys are elided
Date: Mon, 11 Nov 2013 12:20:13 +0100 [thread overview]
Message-ID: <20131111112013.GC15810@gmail.com> (raw)
In-Reply-To: <1383900822-14609-1-git-send-email-namhyung@kernel.org>
* Namhyung Kim <namhyung@kernel.org> wrote:
> From: Namhyung Kim <namhyung.kim@lge.com>
>
> If given sort keys are all elided there'll be no output except for the
> overhead column - actually the TUI shows a noisy output. In this case
> it'd be better to show up the sort keys rather than elide.
>
> Before:
>
> $ perf report -s comm -c perf
> (...)
> # Overhead
> # ........
> #
> 100.00%
>
> After:
>
> $ perf report -s comm -c perf
> (...)
> # Overhead Command
> # ........ .......
> #
> 100.00% perf
>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> tools/perf/util/sort.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/tools/perf/util/sort.c b/tools/perf/util/sort.c
> index 3c1b75c8b9a6..fb7d556ad721 100644
> --- a/tools/perf/util/sort.c
> +++ b/tools/perf/util/sort.c
> @@ -1137,6 +1137,8 @@ static void sort_entry__setup_elide(struct sort_entry *se,
>
> void sort__setup_elide(FILE *output)
> {
> + struct sort_entry *se;
> +
> sort_entry__setup_elide(&sort_dso, symbol_conf.dso_list,
> "dso", output);
> sort_entry__setup_elide(&sort_comm, symbol_conf.comm_list,
> @@ -1172,4 +1174,14 @@ void sort__setup_elide(FILE *output)
> "snoop", output);
> }
>
> + /*
> + * It makes no sense to elide all of sort entries.
> + * Just revert them to show up again.
> + */
> + list_for_each_entry(se, &hist_entry__sort_list, list)
> + if (!se->elide)
> + return;
(Nit: please use curly braces around multi-line statements.)
> +
> + list_for_each_entry(se, &hist_entry__sort_list, list)
> + se->elide = false;
Looks good otherwise - this is the first step in the sort/key behavior
improvements that we talked about a few days ago, right?
Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
next prev parent reply other threads:[~2013-11-11 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 8:53 [PATCH] perf tools: Prevent condition that all sort keys are elided Namhyung Kim
2013-11-11 11:20 ` Ingo Molnar [this message]
2013-11-12 7:14 ` Namhyung Kim
2013-11-12 21:55 ` [tip:perf/urgent] " tip-bot for Namhyung Kim
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=20131111112013.GC15810@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
/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.