public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: perf: confused by cc1
Date: Thu, 31 Dec 2009 11:10:17 +0800	[thread overview]
Message-ID: <4B3C1619.7060001@cn.fujitsu.com> (raw)
In-Reply-To: <20091231014714.GA8313@gallifrey>



Dr. David Alan Gilbert wrote:
> Hi,
>   I'm running 2.6.33rc2 and thought I'd have a play with perf; its
> symbol resolution code seems to be getting itself a bit confused however:
> 
> I recorded a trace of a kernel build like so:
> 
>  sudo /discs/more/git/linux-2.6/tools/perf/perf record -a -e cycles -i -g -v -s -d make -j 8 bzImage
> 
> Then I did:
> /discs/more/git/linux-2.6/tools/perf/perf report -g
> 
> and the top entry is:
> 
>     69.89%              cc1  cc1                                                      [.] 0x000000000337cd
>                         |          
>                         |--0.99%-- 0x9f5da8
>                         |          
>                         |--0.74%-- 0x9eec95
>                          --98.27%-- [...]
> 
> but it's refusing to do symbol look up for cc1 even if I install
> the (ubuntu) debug packages (most other files it is doing
> symbol resolution on where they have it). I dug a bit further and
> it looks like it's not trying to look up the debug packages for cc1
> because it think that mapping is a kernel map.  Also for some reason it
> thinks the cc1 is an overlapping mapping with the gcc4 binary it's been
> executed from:
> 

Your kernel is relocatable? See: http://lkml.org/lkml/2009/12/29/358

Thanks,
Xiao

  reply	other threads:[~2009-12-31  3:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-31  1:47 perf: confused by cc1 Dr. David Alan Gilbert
2009-12-31  3:10 ` Xiao Guangrong [this message]
2009-12-31 12:19   ` Dr. David Alan Gilbert

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=4B3C1619.7060001@cn.fujitsu.com \
    --to=xiaoguangrong@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@treblig.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