From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Arun Sharma <arun@sharma-home.net>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf record regression?
Date: Thu, 10 Mar 2011 11:49:28 -0300 [thread overview]
Message-ID: <20110310144927.GF14438@ghostprotocols.net> (raw)
In-Reply-To: <AANLkTikcz=_HX7Ws2Ojmky+JgQhk1cj2YW=uxSkYkXBQ@mail.gmail.com>
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.
>
> Using git bisect, I narrowed it down to these two commits:
>
> commit f60686f71f4afec7b2925b4682f33c70c0a7eb17
> Author: Arnaldo Carvalho de Melo <acme@redhat.com>
> Date: Wed Mar 9 07:48:24 2011 -0300
>
> perf evsel: Assume rest of perf_header_attr functions
>
> commit e62e48df064b431029658089ab1f8b529ff6da3d
> Author: Arnaldo Carvalho de Melo <acme@redhat.com>
> Date: Tue Mar 8 09:05:57 2011 -0300
>
> perf session: Simplify evlist creation from perf.data header
>
> 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.
- Arnaldo
next prev parent reply other threads:[~2011-03-10 14:49 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 [this message]
2011-03-10 15:28 ` Arnaldo Carvalho de Melo
2011-03-10 16:31 ` 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=20110310144927.GF14438@ghostprotocols.net \
--to=acme@redhat.com \
--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 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.