From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Stephane Eranian <eranian@google.com>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH 4/7] perf diff: Fix to sort by baseline field by default
Date: Tue, 23 Dec 2014 13:12:13 +0900 [thread overview]
Message-ID: <20141223041213.GC14960@sejong> (raw)
In-Reply-To: <20141222144513.GB2717@kernel.org>
On Mon, Dec 22, 2014 at 11:45:13AM -0300, Arnaldo Carvalho de Melo wrote:
> Looks better, here I tried running 'perf record usleep 1' in quick
> succession to then run 'perf diff' before and after this patch, got:
>
> Before:
>
> [ssdandy ~]$ cat /tmp/before
> # Event 'cycles'
> #
> # Baseline Delta Shared Object Symbol
> # ........ ....... ................ ..............................
> #
> +36.29% [kernel.vmlinux] [k] __split_vma.isra.31
> 34.55% [kernel.vmlinux] [k] copy_user_generic_unrolled
> +2.45% [kernel.vmlinux] [k] local_clock
> 0.11% +0.02% [kernel.vmlinux] [k] native_write_msr_safe
> 2.12% [kernel.vmlinux] [k] perf_event_comm_output
> +61.13% [kernel.vmlinux] [k] unmap_page_range
> 63.22% libc-2.17.so [.] 0x000000000007c3e0
> [acme@ssdandy ~]$
>
> After:
>
> [acme@ssdandy linux]$ perf diff
> # Event 'cycles'
> #
> # Baseline Delta Shared Object Symbol
> # ........ ....... ................ ..............................
> #
> 63.22% libc-2.17.so [.] 0x000000000007c3e0
> 34.55% [kernel.vmlinux] [k] copy_user_generic_unrolled
> 2.12% [kernel.vmlinux] [k] perf_event_comm_output
> 0.11% +0.02% [kernel.vmlinux] [k] native_write_msr_safe
> +36.29% [kernel.vmlinux] [k] __split_vma.isra.31
> +2.45% [kernel.vmlinux] [k] local_clock
> +61.13% [kernel.vmlinux] [k] unmap_page_range
> [acme@ssdandy linux]$
>
> Which was ok up to the point where symbols that only appeared on the
> second run were not sorted by delta, can you fix that?
I'll do that later.
>
> Please let me know if it is better to apply this one then a followup to
> sort the deltas or if a combined patch to achieve both is best.
I prefer applying this for now and then improve sorting later..
>
> I.e.:
>
> [acme@ssdandy linux]$ perf diff
> # Event 'cycles'
> #
> # Baseline Delta Shared Object Symbol
> # ........ ....... ................ ..............................
> #
> 63.22% libc-2.17.so [.] 0x000000000007c3e0
> 34.55% [kernel.vmlinux] [k] copy_user_generic_unrolled
> 2.12% [kernel.vmlinux] [k] perf_event_comm_output
> 0.11% +0.02% [kernel.vmlinux] [k] native_write_msr_safe
> +61.13% [kernel.vmlinux] [k] unmap_page_range
> +36.29% [kernel.vmlinux] [k] __split_vma.isra.31
> +2.45% [kernel.vmlinux] [k] local_clock
>
> [acme@ssdandy linux]$
>
> Humm, but then wouldn't we be more interested in sorting _everything_ by
> delta?
I don't understand whay you said.. what do you mean by 'everything be
delta'? Is that something other than perf diff -o 1 ?
Thanks,
Namhyung
next prev parent reply other threads:[~2014-12-23 4:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 4:44 [PATCHSET 0/7] perf tools: A small random cleanup and fixups Namhyung Kim
2014-12-22 4:44 ` [PATCH 1/7] perf report: Get rid of report__inc_stat() Namhyung Kim
2015-01-28 15:04 ` [tip:perf/core] " tip-bot for Namhyung Kim
2014-12-22 4:44 ` [PATCH 2/7] perf report: Show progress bar for output resorting Namhyung Kim
2015-01-01 21:28 ` [tip:perf/urgent] " tip-bot for Namhyung Kim
2014-12-22 4:44 ` [PATCH 3/7] perf ui/tui: Print backtrace symbols when segfault occurred Namhyung Kim
2015-01-01 21:28 ` [tip:perf/urgent] perf ui/tui: Print backtrace symbols when segfault occurs tip-bot for Namhyung Kim
2014-12-22 4:44 ` [PATCH 4/7] perf diff: Fix to sort by baseline field by default Namhyung Kim
2014-12-22 14:45 ` Arnaldo Carvalho de Melo
2014-12-23 4:12 ` Namhyung Kim [this message]
2014-12-23 13:30 ` Arnaldo Carvalho de Melo
2014-12-22 4:44 ` [PATCH 5/7] perf diff: Get rid of hists__compute_resort() Namhyung Kim
2014-12-22 4:44 ` [PATCH 6/7] perf tools: Append callchains only when requested Namhyung Kim
2015-01-01 21:29 ` [tip:perf/urgent] perf callchain: " tip-bot for Namhyung Kim
2015-01-03 2:25 ` [PATCH 6/7] perf tools: " Arnaldo Carvalho de Melo
2015-01-03 15:01 ` Namhyung Kim
2015-01-05 12:49 ` Arnaldo Carvalho de Melo
2015-01-07 7:28 ` Namhyung Kim
2014-12-22 4:44 ` [PATCH 7/7] perf tools: Set attr.task bit for a tracking event Namhyung Kim
2014-12-22 14:49 ` Arnaldo Carvalho de Melo
2014-12-23 4:06 ` Namhyung Kim
2014-12-23 13:28 ` Arnaldo Carvalho de Melo
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=20141223041213.GC14960@sejong \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).