From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Olsa Subject: Re: "perf script" broken with --call-graph=dwarf on recent kernels? Date: Tue, 18 Aug 2015 09:05:48 +0200 Message-ID: <20150818070548.GA23807@krava.local> References: <55D20AF9.9040705@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx1.redhat.com ([209.132.183.28]:50548 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750764AbbHRHFu (ORCPT ); Tue, 18 Aug 2015 03:05:50 -0400 Content-Disposition: inline In-Reply-To: <55D20AF9.9040705@gmail.com> Sender: linux-perf-users-owner@vger.kernel.org List-ID: To: Ben Redelings Cc: linux-perf-users@vger.kernel.org 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