All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: Christoph Bartoschek <bartoschek@gmx.de>,
	linux-perf-users@vger.kernel.org, Arun Sharma <asharma@fb.com>
Subject: Re: Callgraph like kcachegrind
Date: Fri, 06 Jul 2012 09:27:47 +0900	[thread overview]
Message-ID: <87obntlon0.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20120705004428.GA17035@infradead.org> (Arnaldo Carvalho de Melo's message of "Wed, 4 Jul 2012 21:44:28 -0300")

On Wed, 4 Jul 2012 21:44:28 -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Jun 28, 2012 at 02:59:39PM +0200, Christoph Bartoschek escreveu:
>> is it somehow possible to get a callgraph like gets it from kcachegrind?
>> 
>> I tried to use -g/-G on a program that runs but the information is not as 
>> expected. I do not see how the 100% runtime of main() is distributed.
>
> This is a feature we should have, but till then I think there is a
> script out there that does that, lemme try to google that, gack, I know
> there is one, but 'perf tools' really isn't google friendly, anyone?
>

I saw Arun posted a kind of cumulative (or inclusive) call graph patch
long ago. I guess it'd be the first step to have the feature like above.
And IIRC Ingo wanted to have it too.

Arun, what's the state of the patch?

Thanks,
Namhyung

  reply	other threads:[~2012-07-06  0:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 12:59 Callgraph like kcachegrind Christoph Bartoschek
2012-07-05  0:44 ` Arnaldo Carvalho de Melo
2012-07-06  0:27   ` Namhyung Kim [this message]
2012-07-06  0:50     ` Arun Sharma
2012-07-06  1:28       ` Namhyung Kim
2012-07-06  7:40         ` Frederic Weisbecker
2012-07-06 14:58           ` Stand alone perf.data parser (Was Re: Callgraph like kcachegrind) Arun Sharma
2012-07-06 15:12             ` Arnaldo Carvalho de Melo
2012-07-23 13:28   ` Callgraph like kcachegrind Mark Hills

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=87obntlon0.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=acme@infradead.org \
    --cc=asharma@fb.com \
    --cc=bartoschek@gmx.de \
    --cc=linux-perf-users@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.