mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v4 0/5] perf report: Show inline stack
Date: Thu, 16 Mar 2017 21:47:13 +0800	[thread overview]
Message-ID: <5e14721e-57af-b009-06d6-9cd27391b9d9@linux.intel.com> (raw)
In-Reply-To: <148956608.Gr0Z3zOxTt@milian-kdab2>

Hi Wolff,

Thanks so much for your review comments!

I just send out the v5 patch series. The patch series are updated 
according to your comments.

Thanks

Jin Yao

On 3/14/2017 8:59 PM, Milian Wolff wrote:
> On Friday, March 3, 2017 11:43:00 AM CET Jin Yao wrote:
>> v4: Remove the options "--inline-line" and "--inline-name". Just use
>>      a new option "--inline" to print the inline function information.
>>      The policy is if the inline function name can be resolved then
>>      print the name in priority. If the name can't be resolved, then
>>      print the source line number.
> This is still wrong from a usability POV. I may want to see the file/line for
> entry that have a name. And actually, there are afaik no situations where you
> could have a file/line but not a symbol name.
>
> Again, why don't you align this with the other non-inlined frames, and honor
> the grouping setting? Check whether we group by address (then display file/
> line), or by function (then display the function name).
>
> Bye

      reply	other threads:[~2017-03-16 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 10:43 Jin Yao
2017-03-03 10:43 ` [PATCH v4 1/5] perf report: Refactor common code in srcline.c Jin Yao
2017-03-03 10:43 ` [PATCH v4 2/5] perf report: Find the inline stack for a given address Jin Yao
2017-03-03 10:43 ` [PATCH v4 3/5] perf report: Create new inline option Jin Yao
2017-03-03 10:43 ` [PATCH v4 4/5] perf report: Show inline stack in stdio mode Jin Yao
2017-03-03 10:43 ` [PATCH v4 5/5] perf report: Show inline stack in browser mode Jin Yao
2017-03-14  1:16 ` [PATCH v4 0/5] perf report: Show inline stack Jin, Yao
2017-03-14 12:59 ` Milian Wolff
2017-03-16 13:47   ` 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=5e14721e-57af-b009-06d6-9cd27391b9d9@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

Powered by JetHome