From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
mingo@elte.hu, "Peter Zijlstra" <peterz@infradead.org>,
"Tom Zanussi" <tzanussi@gmail.com>,
"Mike Galbraith" <efault@gmx.de>,
"Paul Mackerras" <paulus@samba.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [GIT PULL 0/2] perf annotate fix and report improvoment
Date: Wed, 26 May 2010 17:50:02 -0300 [thread overview]
Message-ID: <20100526205002.GE9874@ghostprotocols.net> (raw)
In-Reply-To: <AANLkTimBC83Z8lSD8Drfpefl1D8Fpx-hYuQaZx4RyvSG@mail.gmail.com>
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@emilia linux-2.6-tip]# perf report -d libc-2.12.so
> > [root@emilia linux-2.6-tip]# perf annotate -d libc-2.12.so
> >
> > with
> >
> > [root@emilia linux-2.6-tip]# cat ~/.perfconfig
> > [tui]
> >
> > report = on
> > annotate = on
> > [root@emilia 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
next prev parent reply other threads:[~2010-05-26 20:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 1:31 [GIT PULL 0/2] perf annotate fix and report improvoment Arnaldo Carvalho de Melo
2010-05-24 1:31 ` [PATCH 1/2] perf report: Support multiple events on the TUI Arnaldo Carvalho de Melo
2010-05-24 1:31 ` [PATCH 2/2] perf annotate: Fix up usage of the build id cache Arnaldo Carvalho de Melo
2010-05-24 7:30 ` [GIT PULL 0/2] perf annotate fix and report improvoment Ingo Molnar
2010-05-25 21:08 ` Stephane Eranian
2010-05-26 0:55 ` Arnaldo Carvalho de Melo
[not found] ` <AANLkTim-xv9mNEwGCueV47AoKh6AXbrdbTdCEwZHaEHJ@mail.gmail.com>
[not found] ` <20100526182351.GB9874@ghostprotocols.net>
2010-05-26 19:07 ` Stephane Eranian
2010-05-26 19:32 ` Arnaldo Carvalho de Melo
2010-05-26 20:11 ` Stephane Eranian
2010-05-26 20:33 ` Arnaldo Carvalho de Melo
2010-05-26 20:40 ` Stephane Eranian
2010-05-26 20:50 ` Arnaldo Carvalho de Melo [this message]
2010-05-26 23:13 ` Stephane Eranian
2010-05-27 0:23 ` 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=20100526205002.GE9874@ghostprotocols.net \
--to=acme@infradead.org \
--cc=davem@davemloft.net \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--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;
as well as URLs for NNTP newsgroup(s).