From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Milian Wolff <milian.wolff@kdab.com>
Cc: acme@kernel.org, jolsa@kernel.org, Linux-kernel@vger.kernel.org,
ak@linux.intel.com, kan.liang@intel.com
Subject: Re: [PATCH v3 0/5] perf report: Show inline stack
Date: Fri, 3 Mar 2017 10:38:40 +0800 [thread overview]
Message-ID: <bd2f8e05-86b0-f419-0d7d-8a7d453a71e9@linux.intel.com> (raw)
In-Reply-To: <7369636.07Z93mMh8K@agathebauer>
Hi Wolff,
Thanks so much for your testing. I also wish this feature could be
upstreamed.
I will send a v4 series soon. In v4, It removes the options
"--inline-line" and "--inline-name".
It just uses a new option "--inline" to print the inline function
information. The policy is if the inline function name can be resolved
then print the function name otherwise it prints the source line number.
For example:
perf report --stdio --inline
It prints:
0.69% 0.00% inline ld-2.23.so [.] dl_main
|
---dl_main
|
--0.56%--_dl_relocate_object
|
---_dl_relocate_object (inline)
elf_dynamic_do_Rela (inline)
Thanks
Jin Yao
On 3/3/2017 5:42 AM, Milian Wolff wrote:
> On Dienstag, 21. Februar 2017 01:28:17 CET Jin, Yao wrote:
>> Hi,
>>
>> Any comments for this patch series?
> Sorry for the delay. I just tested it again.
>
> Overall, this is a clear improvement, so I'm all for getting this
> functionality in.
>
> But from a usability point of view, I still have the some of the issues that I
> have raised in the past:
>
> a) --inline should be a boolean setting that enables inline resolution on
> demand
>
> b) the other callgraph settings and formatting should be used for inlined
> frames, i.e.
>
> - instead of `perf report --inline-name`
> it should be: `perf report --inline -g function`
> and since `-g function` is the default, it would be the same as:
> `perf report --inline`
>
> - instead of `perf report --inline-line -g address`
> it should be: `perf report --inline -g address`
>
> Again: As a user of `perf report`, I do not care whether a frame is an inlined
> one or a non-inlined one - both should be grouped and displayed the same way.
>
> I.e. this is unusable (imo):
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~
> perf report --inline-line --stdio
>
> 99.81% 35.99% cpp-inlining cpp-inlining [.] main
> |
> |--63.82%--main
> |
> ---/home/milian/projects/kdab/rnd/hotspot/tests/test-
> clients/cpp-inlining/main.cpp:39 (inline)
> /usr/include/c++/6.3.1/complex:664 (inline)
> | |
> | |--63.19%--hypot
> | | |
> | | --58.04%--__hypot_finite
> | |
> | --0.62%--cabs
> ~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Dito for this:
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~
> perf report --stdio --inline-name -g address --stdio
>
> 99.81% 35.99% cpp-inlining cpp-inlining [.] main
> |
> |--63.82%--main complex:655
> |
> ---main (inline)
> std::norm<double> (inline)
> ~~~~~~~~~~~~~~~~~~~~~~~~~
>
> But, again, even with these gripes, I think it's a very useful feature and I
> would like to see it integrated upstream. From my POV, you can add
>
> Tested-by: Milian Wolff <milian.wolff@kdab.com>
>
> to all patches in this series.
>
> Many thanks!
>
prev parent reply other threads:[~2017-03-03 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 9:39 [PATCH v3 0/5] perf report: Show inline stack Jin Yao
2017-01-20 9:39 ` [PATCH v3 1/5] perf report: Refactor common code in srcline.c Jin Yao
2017-01-20 9:39 ` [PATCH v3 2/5] perf report: Find the inline stack for a given address Jin Yao
2017-01-20 9:39 ` [PATCH v3 3/5] perf report: Create new inline options Jin Yao
2017-01-20 9:39 ` [PATCH v3 4/5] perf report: Show inline stack in stdio mode Jin Yao
2017-01-20 9:39 ` [PATCH v3 5/5] perf report: Show inline stack in browser mode Jin Yao
2017-02-21 0:28 ` [PATCH v3 0/5] perf report: Show inline stack Jin, Yao
2017-03-02 21:42 ` Milian Wolff
2017-03-03 2:38 ` Jin, Yao [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=bd2f8e05-86b0-f419-0d7d-8a7d453a71e9@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=milian.wolff@kdab.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox