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 14:09:49 +0900 [thread overview]
Message-ID: <8761si9e1u.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20131025150721.GA12534@sdfg.com.ar> (Rodrigo Campos's message of "Fri, 25 Oct 2013 16:07:21 +0100")
Hi Rodrigo,
On Fri, 25 Oct 2013 16:07:21 +0100, Rodrigo Campos wrote:
> Hi Namhyung,
>
> Frederic Weisbecker and Arnaldo Carvalho de Melo told me on IRC that you were
> working to forward-port a patch that adds a new sort order to perf report,
> SORT_INCLUSIVE.
>
> That will be useful for me and I was wondering if you are still working on that
> or if there is a newer version than v6:
>
> http://thread.gmane.org/gmane.linux.kernel.perf.user/882
>
>
> Maybe you have a newer version of it not sent to the list ? Or do you plan to
> work on it anytime soon ?
>
> If there is any branch to test, please let me know :)
Yes I have a patch series for that. But it's not a new sort order but a
new command line option --culumate. I don't think it should be a new
sort order since it affects only how it counts period value on each
sample not how samples are sorted/grouped.
It's about a year since I sent this series to list. I'll work on it and
send it to the list soon. But before that I have to re-read what's the
Frederic's concern - IIRC it's about consolidating code in perf report
that does similar things on branch stack.
Frederic, can you remember what was the problem?
Anyway, You can find the series and discussion on the link below:
https://lkml.org/lkml/2012/9/13/81
Thanks,
Namhyung
next prev parent reply other threads:[~2013-10-28 5: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 [this message]
2013-10-28 8:42 ` Rodrigo Campos
2013-10-28 9:09 ` Namhyung Kim
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=8761si9e1u.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