All of lore.kernel.org
 help / color / mirror / Atom feed
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:33:16 -0300	[thread overview]
Message-ID: <20100526203315.GD9874@ghostprotocols.net> (raw)
In-Reply-To: <AANLkTinxVsp1qtfqjlwl-ngrcD9IBDg6GoBnAk07ABuo@mail.gmail.com>

Em Wed, May 26, 2010 at 10:11:14PM +0200, Stephane Eranian escreveu:
> On Wed, May 26, 2010 at 9:32 PM, Arnaldo Carvalho de Melo
> <acme@infradead.org> wrote:
> > Em Wed, May 26, 2010 at 09:07:05PM +0200, Stephane Eranian escreveu:
> >> But in this example, I only really care about the symbols in the
> >> noploop program (/tmp/noploop).
> >>
> >> Missing symbol support for the kernel should not cause perf to avoid
> >> trying to resolve the symbols in other modules such as my user program
> >> here.
> >
> > Right, my bad, I thought that the problem was about the kernel symbols.
> >
> > Then can you try replacing:
> >
> > perf annotate -i ~/perf.data noploop
> >
> > with:
> >
> > perf annotate -i ~/perf.data -d noploop
> >
> > And see if that helps?
> >
> Ok that works. But if I turned on TUI, then I cannot obtain
> the same result. I am guessing it does not use the -d option.

Humm, it should be working, i.e. -d processing is about adding a filter,
lemme see...

Yeah, in builtin-annotate.c

        OPT_STRING('d', "dsos", &symbol_conf.dso_list_str, "dso[,dso...]",
                   "only consider symbols in these dsos"),

It sets the dso_list_str and that is used when processing events in:

	perf_session__process_events
		process_sample_event (in builtin-annotate.c)
			event__preprocess_sample

In event__preprocess_sample:

     if (symbol_conf.dso_list &&
         (!al->map || !al->map->dso ||
          !(strlist__has_entry(symbol_conf.dso_list,
                               al->map->dso->short_name) ||
            (al->map->dso->short_name != al->map->dso->long_name &&
             strlist__has_entry(symbol_conf.dso_list,
                                al->map->dso->long_name)))))
             goto out_filtered;

Yeah, this is all done no matter what frontend is used :-\

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.

- Arnaldo

  reply	other threads:[~2010-05-26 20:33 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 [this message]
2010-05-26 20:40                 ` Stephane Eranian
2010-05-26 20:50                   ` Arnaldo Carvalho de Melo
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=20100526203315.GD9874@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.