From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Milian Wolff <milian.wolff@kdab.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Jiri Olsa <jolsa@kernel.org>, "Liang, Kan" <kan.liang@intel.com>
Subject: Re: Inlined functions in perf report
Date: Wed, 21 Dec 2016 10:58:23 +0100 [thread overview]
Message-ID: <20161221095823.GA19249@sesse.net> (raw)
In-Reply-To: <df263fe1-e1af-881b-311e-5329bb51db0e@linux.intel.com>
On Wed, Dec 21, 2016 at 08:53:33AM +0800, Jin, Yao wrote:
> I just pull my repo with the latest perf/core branch, and apply the patch
> one by one (git am 0001/0002/.../0005), they can be applied. Maybe you have
> to do like that because the mails are probably coming out of order.
OK. I applied everything on top of the branch you suggested, and now it's
compiling. But seemingly I don't have too much success; on a quick check
(perf record -p <pid> -g, perf report --inline) I don't get anything marked
as (inline), but I get these warnings:
BFD: Dwarf Error: found dwarf version '6931', this reader only handles version 2, 3 and 4 information.
BFD: Dwarf Error: found dwarf version '18896', this reader only handles version 2, 3 and 4 information.
and so on for many seemingly random version numbers.
It may have been that the stack traces I happened to check don't actually
have any inlined functions in them (the load was a bit different from what
I've looked at earlier), but the BFD errors are new from what I can see.
/* Steinar */
--
Homepage: https://www.sesse.net/
next prev parent reply other threads:[~2016-12-21 9:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 11:59 Inlined functions in perf report Steinar H. Gunderson
2016-12-20 12:17 ` Peter Zijlstra
2016-12-20 13:27 ` Milian Wolff
2016-12-20 13:43 ` Steinar H. Gunderson
2016-12-20 14:03 ` Milian Wolff
2016-12-20 13:54 ` Arnaldo Carvalho de Melo
2016-12-20 14:05 ` Milian Wolff
2016-12-20 14:08 ` Steinar H. Gunderson
2016-12-20 14:37 ` Arnaldo Carvalho de Melo
2016-12-20 17:01 ` Steinar H. Gunderson
2016-12-21 0:53 ` Jin, Yao
2016-12-21 9:58 ` Steinar H. Gunderson [this message]
2016-12-21 10:09 ` Milian Wolff
2016-12-21 10:20 ` Steinar H. Gunderson
2016-12-21 22:56 ` Jin, Yao
2016-12-21 22:58 ` Steinar H. Gunderson
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=20161221095823.GA19249@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.com \
--cc=peterz@infradead.org \
--cc=yao.jin@linux.intel.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.