From: Namhyung Kim <namhyung@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHSET 0/4] perf diff: Introduce delta-abs compute method (v2)
Date: Fri, 10 Feb 2017 18:14:43 +0900 [thread overview]
Message-ID: <20170210091443.GA17307@danjae.aot.lge.com> (raw)
In-Reply-To: <20170210074111.GB14923@gmail.com>
Hi Ingo,
On Fri, Feb 10, 2017 at 08:41:11AM +0100, Ingo Molnar wrote:
>
> * Namhyung Kim <namhyung@kernel.org> wrote:
>
> > Hello,
> >
> > This patchset adds 'delta-abs' compute method to -c/--compute option.
> > The 'delta-abs' is same as 'delta' but shows entries with bigger
> > absolute delta first instead of sorting numerically. This is only
> > useful together with -o option.
> >
> > * v2 changes
> > - rebase onto acme/perf/core
> > - change default option to '-o 1 -c delta-abs'
> >
> >
> > Below is default output (-c delta):
> >
> > $ perf diff -o 1 -c delta | grep -v ^# | head
> > 42.22% +4.97% [kernel.kallsyms] [k] cfb_imageblit
> > 0.62% +1.23% [kernel.kallsyms] [k] mutex_lock
> > +1.15% [kernel.kallsyms] [k] copy_user_generic_string
> > 2.40% +0.95% [kernel.kallsyms] [k] bit_putcs
> > 0.31% +0.79% [kernel.kallsyms] [k] link_path_walk
> > +0.64% [kernel.kallsyms] [k] kmem_cache_alloc
> > 0.00% +0.57% [kernel.kallsyms] [k] __rcu_read_unlock
> > +0.45% [kernel.kallsyms] [k] alloc_set_pte
> > 0.16% +0.45% [kernel.kallsyms] [k] menu_select
> > +0.41% ld-2.24.so [.] do_lookup_x
> >
> > Now with 'delta-abs' it shows entries have bigger delta value either
> > positive or negative.
> >
> > $ perf diff -o 1 -c delta-abs | grep -v ^# | head
> > 42.22% +4.97% [kernel.kallsyms] [k] cfb_imageblit
> > 12.72% -3.01% [kernel.kallsyms] [k] intel_idle
> > 9.72% -1.31% [unknown] [.] 0x0000000000411343
> > 0.62% +1.23% [kernel.kallsyms] [k] mutex_lock
> > +1.15% [kernel.kallsyms] [k] copy_user_generic_string
> > 2.40% +0.95% [kernel.kallsyms] [k] bit_putcs
> > 0.31% +0.79% [kernel.kallsyms] [k] link_path_walk
> > 1.35% -0.71% [kernel.kallsyms] [k] smp_call_function_single
> > +0.64% [kernel.kallsyms] [k] kmem_cache_alloc
> > 0.00% +0.57% [kernel.kallsyms] [k] __rcu_read_unlock
>
> Nice!
>
> BTW., to me the second output looks a lot more intuitive and useful than the
> default one.
Thanks!
>
> Would it be possible to flip over the default to the 'most useful' options, and
> see whether anyone complains?
The patch 4 makes it default.
By the way, the current default (sort by baseline) looks like below:
$ perf diff | grep -v ^# | head
42.22% +4.97% [kernel.kallsyms] [k] cfb_imageblit
12.72% -3.01% [kernel.kallsyms] [k] intel_idle
9.72% -1.31% [unknown] [.] 0x0000000000411343
2.40% +0.95% [kernel.kallsyms] [k] bit_putcs
1.35% -0.71% [kernel.kallsyms] [k] smp_call_function_single
0.62% +1.23% [kernel.kallsyms] [k] mutex_lock
0.31% +0.79% [kernel.kallsyms] [k] link_path_walk
0.16% +0.45% [kernel.kallsyms] [k] menu_select
0.00% +0.57% [kernel.kallsyms] [k] __rcu_read_unlock
While this example doesn't show much difference, it could be..
Thanks,
Namhyung
next prev parent reply other threads:[~2017-02-10 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 7:36 Namhyung Kim
2017-02-10 7:36 ` [PATCH v2 1/4] perf diff: Add 'delta-abs' compute method Namhyung Kim
2017-02-14 6:38 ` [tip:perf/core] " tip-bot for Namhyung Kim
2017-02-10 7:36 ` [PATCH v2 2/4] perf diff: Add diff.order config option Namhyung Kim
2017-02-14 6:38 ` [tip:perf/core] " tip-bot for Namhyung Kim
2017-02-10 7:36 ` [PATCH v2 3/4] perf diff: Add diff.compute " Namhyung Kim
2017-02-14 6:39 ` [tip:perf/core] " tip-bot for Namhyung Kim
2017-02-10 7:36 ` [PATCH v2 4/4] perf diff: Change default setting to "delta-abs" Namhyung Kim
2017-02-10 16:18 ` [PATCH v2.1 " Namhyung Kim
2017-02-14 6:39 ` [tip:perf/core] " tip-bot for Namhyung Kim
2017-02-10 7:41 ` [PATCHSET 0/4] perf diff: Introduce delta-abs compute method (v2) Ingo Molnar
2017-02-10 9:14 ` Namhyung Kim [this message]
2017-02-10 10:29 ` Ingo Molnar
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=20170210091443.GA17307@danjae.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®