From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Arun Sharma <arun@sharma-home.net>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf record regression?
Date: Thu, 10 Mar 2011 13:31:09 -0300 [thread overview]
Message-ID: <20110310163109.GD23555@ghostprotocols.net> (raw)
In-Reply-To: <20110310152807.GA23555@ghostprotocols.net>
Em Thu, Mar 10, 2011 at 12:28:07PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Mar 10, 2011 at 11:49:28AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Wed, Mar 09, 2011 at 09:59:39PM -0800, Arun Sharma escreveu:
> > > I pulled the perf/core branch in
> > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux-2.6.git today
> > > and found that:
> > >
> > > perf record -ag -- sleep 1
> > > perf report -D | grep dso:
> > >
> > > was returning:
> > >
> > > ...... dso: <not found>
> > > ...... dso: <not found>
> > > ...... dso: /boot/vmlinux-2.6.38-rc5+
> > >
> > > i.e perf report was not able to map IP addresses to the correct dso
> > > for anything in user space.
> > > perf built after these commits is able to symbolize properly for
> > > perf.data collected using an older version of perf. So I believe, the
> > > perf report side of things are ok. But perf record is not.
> >
> > Thanks for bisecting, I noticed some problems yesterday and was trying
> > to bisect it, but run into another bug, will investigate now.
>
> Can you try with this one? Has the fix plus some simplifications.
Ah, just noticed that Ingo didn't merge this branch due to some other
isues with 'perf script' patches from David Ahern, so I'll just fold
this before resubmitting to him, so that we remove this problem from our
bisectable upstream :-)
- Arnaldo
prev parent reply other threads:[~2011-03-10 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 5:59 perf record regression? Arun Sharma
2011-03-10 14:49 ` Arnaldo Carvalho de Melo
2011-03-10 15:28 ` Arnaldo Carvalho de Melo
2011-03-10 16:31 ` 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=20110310163109.GD23555@ghostprotocols.net \
--to=acme@infradead.org \
--cc=arun@sharma-home.net \
--cc=linux-perf-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).