The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] perf report is broken in latest linus git
Date: Thu, 13 Aug 2009 11:36:48 +0200	[thread overview]
Message-ID: <20090813093648.GA22762@elte.hu> (raw)
In-Reply-To: <1250155708.6052.2.camel@penberg-laptop>


* Pekka Enberg <penberg@cs.helsinki.fi> wrote:

> Latest Linus git kernel with -rc4 perf userspace:
> 
>   penberg@penberg-laptop:~/testing/jato$ perf record -f jato HelloWorldSwing
>   [ perf record: Captured and wrote 1.402 MB perf.data (~61261 samples) ]
> 
>   penberg@penberg-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

  reply	other threads:[~2009-08-13  9:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13  9:28 [PROBLEM] perf report is broken in latest linus git Pekka Enberg
2009-08-13  9:36 ` Ingo Molnar [this message]
2009-08-13  9:47   ` Pekka Enberg
2009-08-13 11:33     ` Peter Zijlstra
2009-08-13 12:02       ` Pekka Enberg
2009-08-13 12:24         ` Pekka Enberg
2009-08-13 14:14 ` [PATCH] perf_counter: Report the cloning task as parent on perf_counter_fork() Peter Zijlstra
2009-08-13 14:18   ` [tip:perfcounters/urgent] " tip-bot for Peter Zijlstra
2009-08-15  8:58   ` [PATCH] " Pekka Enberg
2009-08-15  9:13     ` 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=20090813093648.GA22762@elte.hu \
    --to=mingo@elte.hu \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=peterz@infradead.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