From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, paulus@samba.org, davem@davemloft.net,
fweisbec@gmail.com, perfmon2-devel@lists.sf.net,
eranian@gmail.com, tzanussi@gmail.com
Subject: Re: how to use perf annotate on the kernel
Date: Thu, 3 Jun 2010 21:20:39 -0300 [thread overview]
Message-ID: <20100604002039.GC10469@ghostprotocols.net> (raw)
In-Reply-To: <AANLkTincvUH7p-aHsDZoThUQn_eZkdbq3A8bM5i5ytpo@mail.gmail.com>
Em Thu, Jun 03, 2010 at 08:18:04PM +0200, Stephane Eranian escreveu:
> perf annotate __lock_acquire -k /home/eranian/perfmon/official/tip/build/vmlinux
> build id event received for [kernel.kallsyms]:
> 5c110a704293a259fbe11158dc1b25107ad7a23e
> build id event received for
> /lib/modules/2.6.35-rc1-tip/kernel/arch/x86/kernel/cpu/cpufreq/mperf.ko:
> cb5
> build id event received for
> /lib/modules/2.6.35-rc1-tip/kernel/drivers/cpufreq/cpufreq_ondemand.ko:
> cdb5
> Using /home/eranian/perfmon/official/tip/build/vmlinux for symbols
> hist_entry__inc_addr_samples: ip=0xffffffff81073b36
> 0xffffffff81073b30 __lock_acquire: period++ [ip: 0xffffffff81073b36, 0x6] => 1
> hist_entry__inc_addr_samples: ip=0xffffffff81073c94
>
> But in the end I get:
> objdump: '[kernel.kallsyms]': No such file
Reproduced, working on it now. I've been testing only with vmlinux in
the path it searches for, not by directly specifying it, will get that
fixed, thanks,
- Arnaldo
next prev parent reply other threads:[~2010-06-04 0:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 17:23 how to use perf annotate on the kernel Stephane Eranian
2010-06-03 17:54 ` Arnaldo Carvalho de Melo
2010-06-03 18:06 ` Arnaldo Carvalho de Melo
2010-06-03 18:11 ` Arnaldo Carvalho de Melo
2010-06-03 18:18 ` Stephane Eranian
2010-06-04 0:20 ` Arnaldo Carvalho de Melo [this message]
2010-06-04 0:39 ` Arnaldo Carvalho de Melo
2010-06-04 8:55 ` Stephane Eranian
2010-06-03 18:12 ` Stephane Eranian
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=20100604002039.GC10469@ghostprotocols.net \
--to=acme@infradead.org \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=perfmon2-devel@lists.sf.net \
--cc=peterz@infradead.org \
--cc=tzanussi@gmail.com \
/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