From: Jiri Olsa <jolsa@redhat.com>
To: Ben Redelings <benjamin.redelings@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: "perf script" broken with --call-graph=dwarf on recent kernels?
Date: Tue, 18 Aug 2015 09:05:48 +0200 [thread overview]
Message-ID: <20150818070548.GA23807@krava.local> (raw)
In-Reply-To: <55D20AF9.9040705@gmail.com>
On Mon, Aug 17, 2015 at 12:25:29PM -0400, Ben Redelings wrote:
SNIP
> (/home/bredelings/Devel/bali-phy/local/clang-3.7/bin/bali-phy)
> 306ce1 empirical_frequencies
> (/home/bredelings/Devel/bali-phy/local/clang-3.7/bin/bali-phy)
> 3330d9 get_smodel
> (/home/bredelings/Devel/bali-phy/local/clang-3.7/bin/bali-phy)
> 4dc133 get_smodels
> (/home/bredelings/Devel/bali-phy/local/clang-3.7/bin/bali-phy)
> 4e02ea create_A_and_T_model
> (/home/bredelings/Devel/bali-phy/local/clang-3.7/bin/bali-phy)
>
> This is more what I was expecting, and similar to what I used to get with
> --call-graph=dwarf.
>
> However, the call chains that I get using DWARF tend to be longer and lead
> to more accurate results, so I would prefer to use DWARF instead of lbr. Is
> there something that I'm doing wrong? Also, it seems like
> --call-graph=dwarf successfully records call chains that can be seen via
> perf report, but somehow 'perf script' doesn't show them. Could that
> happen?
>
> -BenRI
>
> P.S. I'm using debian's kernel 4.1.0 and perf tools on a Core i3-4030.
hum, it's probably fixed already:
http://marc.info/?l=linux-kernel&m=143945026316969&w=2
it's currently in Arnaldo's perf/core branch
jirka
next prev parent reply other threads:[~2015-08-18 7:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 16:25 "perf script" broken with --call-graph=dwarf on recent kernels? Ben Redelings
2015-08-18 7:05 ` Jiri Olsa [this message]
2015-08-18 18:28 ` Ben Redelings
2015-10-31 13:25 ` Inverted call-graph broken? Ben Redelings
2015-11-01 14:09 ` Milian Wolff
2015-11-02 17:31 ` Arnaldo Carvalho de Melo
2015-11-02 18:29 ` Milian Wolff
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=20150818070548.GA23807@krava.local \
--to=jolsa@redhat.com \
--cc=benjamin.redelings@gmail.com \
--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).