public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jamie Iles <jamie@jamieiles.com>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: Jamie Iles <jamie.iles@picochip.com>,
	linux-kernel@vger.kernel.org, Jamie Iles <jamie@jamieiles.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] perf symbols: don't use modules or try vmlinux unless needed
Date: Fri, 8 Jan 2010 11:54:06 +0000	[thread overview]
Message-ID: <20100108115406.GL4179@wear.picochip.com> (raw)
In-Reply-To: <20100108113657.GE12660@ghostprotocols.net>

On Fri, Jan 08, 2010 at 09:36:57AM -0200, Arnaldo Carvalho de Melo wrote:
> Ecanfcan Mon, Jan 04, 2010 at 10:23:54AM +0000, Jamie Iles escreveu:
> > Commit 75be6cf (perf symbols: Make symbol_conf global) does what it says
> > on the tin, but also initialises the member fields use_modules and
> > try_vmlinux_path to true rather than the 'false' value they would have
> > had when symbol_conf was static.
> > 
> > When there is no vmlinux on the system and modules loaded, perf top will
> > not show any kernel symbols and perf report will only list raw IP's
> > rather than symbol names. Unloading the modules will allow perf to give
> > normal output.
> > 
> > Restore previous behaviour by initialising these fields to false.
> 
> James,
> 
> 	I just tried using perf top here in such conditions:
> 
[snip]
> 
> And it is resolving the kernel symbols.
> 
> Maybe some changes I made that aren't yet in Ingo's tree or upstream
> fixed it, can you please try after those patches are merged?
Ok, could you let me know when the relevant ones are in there? From todays
next tree, without the patch I still only get userspace symbols (system loaded
with 'dd if=/dev/zero of=/dev/null' to make sure it's busy):

               49.00 17.6% T.276                   /root/tools/perf    
               25.00  9.0% __GI_strcmp             /lib/libc-2.8.so    
               21.00  7.6% symbol_filter           /root/tools/perf    
               17.00  6.1% strncmp                 /root/tools/perf    
	       ...

But with the patch applied output looks good:

              597.00 17.0% _raw_spin_unlock_irq        [kernel.kallsyms]
              589.00 16.8% lock_acquire                [kernel.kallsyms]
              367.00 10.4% _raw_spin_unlock_irqrestore [kernel.kallsyms]
              230.00  6.5% vector_swi                  [kernel.kallsyms]
              122.00  3.5% __memzero                   [kernel.kallsyms]
               71.00  2.0% lock_release                [kernel.kallsyms]
	       ...

Jamie

  reply	other threads:[~2010-01-08 11:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04 10:23 [PATCH] perf symbols: don't use modules or try vmlinux unless needed Jamie Iles
2010-01-08 11:36 ` Arnaldo Carvalho de Melo
2010-01-08 11:54   ` Jamie Iles [this message]
     [not found]     ` <20100108123035.GA7485@ghostprotocols.net>
     [not found]       ` <20100108124244.GO4179@wear.picochip.com>
     [not found]         ` <20100108125521.GB7485@ghostprotocols.net>
     [not found]           ` <20100118163332.GA5789@wear.picochip.com>
     [not found]             ` <20100118171035.GD14636@ghostprotocols.net>
     [not found]               ` <20100118202451.GA4167@wear.picochip.com>
     [not found]                 ` <20100119000134.GE14636@ghostprotocols.net>
     [not found]                   ` <20100119000345.GF14636@ghostprotocols.net>
     [not found]                     ` <20100119091231.GC4167@wear.picochip.com>
2010-01-19 13:09                       ` Analysing an ARM perf.data file on a x86-64 workstation Arnaldo Carvalho de Melo
2010-01-19 13:51                         ` Jamie Iles
2010-01-19 14:30                           ` 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=20100108115406.GL4179@wear.picochip.com \
    --to=jamie@jamieiles.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=jamie.iles@picochip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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