From: Namhyung Kim <namhyung@kernel.org>
To: Rodrigo Campos <rodrigo@sdfg.com.ar>
Cc: namhyung.kim@lge.com, linux-kernel@vger.kernel.org,
acme@ghostprotocols.net, asharma@fb.com, fweisbec@gmail.com
Subject: Re: State of "perf: Add a new sort order: SORT_INCLUSIVE"
Date: Mon, 28 Oct 2013 18:09:30 +0900 [thread overview]
Message-ID: <877gcx92yd.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20131028084244.GA7482@sdfg.com.ar> (Rodrigo Campos's message of "Mon, 28 Oct 2013 08:42:44 +0000")
On Mon, 28 Oct 2013 08:42:44 +0000, Rodrigo Campos wrote:
> On Mon, Oct 28, 2013 at 02:09:49PM +0900, Namhyung Kim wrote:
>> Anyway, You can find the series and discussion on the link below:
>>
>> https://lkml.org/lkml/2012/9/13/81
>
> I've read the cover letter for that series and probably because I don't know
> about perf internals I have a question: How will "--culumate" interact with
> "--sort=dso" for example ?
>
> I mean, is it possible for that to show more than 100% ? (if you add all the
> 93.35% in your example in the cover letter, or something similar). Or
> "--culumate --sort=dso" will just group together all entries that have a dso in
> the call chain ?
Hmm.. I think --cumulate option is only meaningful when sort order
includes symbol. Maybe I can add support for --sort=dso case as well
but not sure it's worth. Do you think it's really needed?
>
> Sorry if the question was too obvious if I knew about perf internals :S
No need to sorry about it. :)
Thanks,
Namhyung
next prev parent reply other threads:[~2013-10-28 9:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 15:07 State of "perf: Add a new sort order: SORT_INCLUSIVE" Rodrigo Campos
2013-10-28 5:09 ` Namhyung Kim
2013-10-28 8:42 ` Rodrigo Campos
2013-10-28 9:09 ` Namhyung Kim [this message]
2013-10-28 9:29 ` Rodrigo Campos
2013-10-28 16:43 ` Arun Sharma
2013-10-29 3:11 ` Namhyung Kim
2013-10-29 4:10 ` Arun Sharma
2013-10-29 5:25 ` Namhyung Kim
2013-10-29 8:36 ` Frederic Weisbecker
2013-10-28 8:49 ` Frederic Weisbecker
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=877gcx92yd.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=acme@ghostprotocols.net \
--cc=asharma@fb.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung.kim@lge.com \
--cc=rodrigo@sdfg.com.ar \
/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