[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100526205002.GE9874@ghostprotocols.net>
Date: Wed, 26 May 2010 17:50:02 -0300
From: Arnaldo Carvalho de Melo <acme@...radead.org>
To: Stephane Eranian <eranian@...gle.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Frédéric Weisbecker <fweisbec@...il.com>,
mingo@...e.hu, Peter Zijlstra <peterz@...radead.org>,
Tom Zanussi <tzanussi@...il.com>,
Mike Galbraith <efault@....de>,
Paul Mackerras <paulus@...ba.org>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [GIT PULL 0/2] perf annotate fix and report improvoment
Em Wed, May 26, 2010 at 10:40:24PM +0200, Stephane Eranian escreveu:
> On Wed, May 26, 2010 at 10:33 PM, Arnaldo Carvalho de Melo
> > I just tried it here with:
> >
> > [root@...lia linux-2.6-tip]# perf report -d libc-2.12.so
> > [root@...lia linux-2.6-tip]# perf annotate -d libc-2.12.so
> >
> > with
> >
> > [root@...lia linux-2.6-tip]# cat ~/.perfconfig
> > [tui]
> >
> > report = on
> > annotate = on
> > [root@...lia linux-2.6-tip]#
> >
> > And it works as expected.
> I did not explain my testcase enough ;-<
>
> With TUI, I started from perf report -i perf.data, then chose to zoom into
> the noploop symbol.
You can zoom into DSOs and threads, additionally you can Annotate
symbols, so you mean that annotating the 'noploop' in the 'noploop' DSO
didn't work?
Lets try this offline thing ourselves, can you please put the
perf.data.tar.bz2 and the perf.data files somewhere I can grab? So that
I can try to do these operations here and figure out the problem :-)
I guess there is nothing sensitive in those files, lemme know if making
them available is not an option and I'll try other ways to get this
fixed.
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists