[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090813093648.GA22762@elte.hu>
Date: Thu, 13 Aug 2009 11:36:48 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Pekka Enberg <penberg@...helsinki.fi>
Cc: Peter Zijlstra <peterz@...radead.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
paulus@...ba.org, linux-kernel@...r.kernel.org
Subject: Re: [PROBLEM] perf report is broken in latest linus git
* Pekka Enberg <penberg@...helsinki.fi> wrote:
> Latest Linus git kernel with -rc4 perf userspace:
>
> penberg@...berg-laptop:~/testing/jato$ perf record -f jato HelloWorldSwing
> [ perf record: Captured and wrote 1.402 MB perf.data (~61261 samples) ]
>
> penberg@...berg-laptop:~/testing/jato$ perf report --sort comm,dso,symbol|head -30
> # Samples: 60457
> #
> # Overhead Command Shared Object Symbol
> # ........ ....... ....................................... ......
> #
>
> [ Note: the jato executable doesn't appear anywhere in the trace. I'm
> pretty sure the libzip functions, for example, are from jato, not perf. ]
>
> 36.14% perf /home/penberg/bin/perf [.] dso__synthesize_plt_symbols
> 35.20% perf /home/penberg/bin/perf [.] dso__new
> 3.57% perf /home/penberg/bin/jato [.] 0x0000000000c910
Perhaps it's this commit:
4d1e00a: perf symbol: Fix symbol parsing in certain cases: use the build-id as a symlink
it does not revert cleanly, so you might want to check out these two
commits:
4d1e00a
4d1e00a~1
and build perf on both, and check with your anomalous perf.data
(without changing it) whether the output makes most sense.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists