Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751862Ab0ASOaw (ORCPT ); Tue, 19 Jan 2010 09:30:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750733Ab0ASOav (ORCPT ); Tue, 19 Jan 2010 09:30:51 -0500 Received: from casper.infradead.org ([85.118.1.10]:47472 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750732Ab0ASOau (ORCPT ); Tue, 19 Jan 2010 09:30:50 -0500 Date: Tue, 19 Jan 2010 12:30:37 -0200 From: Arnaldo Carvalho de Melo To: Jamie Iles Cc: linux-perf-users@vger.kernel.org, =?iso-8859-1?Q?Fr=E9d=E9ric?= Weisbecker , Mike Galbraith , Peter Zijlstra , Paul Mackerras , Ingo Molnar , Linux Kernel Mailing List Subject: Re: Analysing an ARM perf.data file on a x86-64 workstation Message-ID: <20100119143037.GH14636@ghostprotocols.net> References: <20100108124244.GO4179@wear.picochip.com> <20100108125521.GB7485@ghostprotocols.net> <20100118163332.GA5789@wear.picochip.com> <20100118171035.GD14636@ghostprotocols.net> <20100118202451.GA4167@wear.picochip.com> <20100119000134.GE14636@ghostprotocols.net> <20100119000345.GF14636@ghostprotocols.net> <20100119091231.GC4167@wear.picochip.com> <20100119130958.GG14636@ghostprotocols.net> <20100119135145.GG4167@wear.picochip.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100119135145.GG4167@wear.picochip.com> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.5.20 (2009-08-17) X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1046 Lines: 25 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/