From: Taeung Song <treeze.taeung@gmail.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
perf group <linux-perf-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [Suggestion/Problems] perf annoate: Some problems related to the source code view and Improvement of it with line numbers
Date: Sat, 18 Feb 2017 09:15:49 +0900 [thread overview]
Message-ID: <28f6e48a-9c4e-82e8-d48a-6b5f7aaae768@gmail.com> (raw)
In-Reply-To: <20170217132939.GA4109@kernel.org>
On 02/17/2017 10:29 PM, Arnaldo Carvalho de Melo wrote:
> Em Fri, Feb 17, 2017 at 11:33:29AM +0900, Taeung Song escreveu:
>> Hi, Arnaldo :)
>>
>> Regarding perf annotate:
>>
>> 1) Problem : wrong line numbers on perf-annotate (both stdio and TUI)
>> 2) Problem : wrong sum of overhead(percent) matching source lines
>> 3) Suggestion : new option showing only source code per function
>> with overhead info (to be more readable :) )
>>
>> I'll send the patchset for them, maybe it'll a bit take time.
>> But I won't be long..
>
> Concentrate on the first, send the patch, while waiting for review, work
> on the second, and so on :-)
>
> - Arnaldo
>
Understood!
I appreciate your concern :)
Thanks,
Taeung
prev parent reply other threads:[~2017-02-18 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 12:34 [Suggestion/Problems] perf annoate: Some problems related to the source code view and Improvement of it with line numbers Taeung Song
2017-02-15 13:24 ` Arnaldo Carvalho de Melo
2017-02-15 14:24 ` Taeung Song
2017-02-17 2:33 ` Taeung Song
2017-02-17 13:29 ` Arnaldo Carvalho de Melo
2017-02-18 0:15 ` Taeung Song [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=28f6e48a-9c4e-82e8-d48a-6b5f7aaae768@gmail.com \
--to=treeze.taeung@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).