From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Jamie Iles <jamie.iles@picochip.com>
Cc: linux-perf-users@vger.kernel.org,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Mike Galbraith" <efault@gmx.de>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Paul Mackerras" <paulus@samba.org>,
"Ingo Molnar" <mingo@elte.hu>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Analysing an ARM perf.data file on a x86-64 workstation
Date: Tue, 19 Jan 2010 12:30:37 -0200 [thread overview]
Message-ID: <20100119143037.GH14636@ghostprotocols.net> (raw)
In-Reply-To: <20100119135145.GG4167@wear.picochip.com>
Em Tue, Jan 19, 2010 at 01:51:45PM +0000, Jamie Iles escreveu:
> Hi Arnaldo,
>
> On Tue, Jan 19, 2010 at 11:09:58AM -0200, Arnaldo Carvalho de Melo wrote:
> > CCing linux-perf-users, this may be interesting when investigating
> > similar problems for other arches.
> >
> > Thanks James, got the vmlinux file and and already found and fixed two
> > bugs, patches sent CCed to you.
> >
> > Ok, now how does it look like?
> Well, with both patches applied, I still don't see any kernel symbols in perf
> top (even the raw addresses) or resolved names in report if I specify a
> vmlinux or if one gets autodetected.
What if you try to do what I did, i.e. to try to decode the perf.data
file on your x86 workstation? Does specifying --vmlinux
/path/to/arm-vmlinux gets the symbols decoded?
- Arnaldo
prev parent reply other threads:[~2010-01-19 14:30 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
[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 [this message]
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=20100119143037.GH14636@ghostprotocols.net \
--to=acme@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=jamie.iles@picochip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--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