From: Frederic Weisbecker <fweisbec@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arun Sharma <asharma@fb.com>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Christoph Bartoschek <bartoschek@gmx.de>,
linux-perf-users@vger.kernel.org
Subject: Re: Callgraph like kcachegrind
Date: Fri, 6 Jul 2012 09:40:21 +0200 [thread overview]
Message-ID: <20120706074018.GA7728@somewhere.redhat.com> (raw)
In-Reply-To: <CAM9d7cjaRxCgwi2QM5dd3w59mORJ5wo8k9DO71d5AhhL5Fvo=g@mail.gmail.com>
On Fri, Jul 06, 2012 at 10:28:28AM +0900, Namhyung Kim wrote:
> Hi,
>
> On Fri, Jul 6, 2012 at 9:50 AM, Arun Sharma <asharma@fb.com> wrote:
> > On 7/5/12 5:27 PM, Namhyung Kim wrote:
> >>
> >> 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?
> >>
> >
> > http://thread.gmane.org/gmane.linux.kernel.perf.user/882 is the most recent
> > patch I posted.
> >
> > The last comments I got were:
> >
> > * Use a global flag instead of a sort mode
> > * Try to integrate with LBR, branch filtering mode.
> >
> > Unfortunately, I'm tied up with other projects right now and am not able to
> > finish this up. Happy to answer questions about the patch if anyone wants to
> > take it over.
> >
>
> Ok, I'll try to look at it.
>
>
> > http://thread.gmane.org/gmane.linux.kernel.perf.user/857 (callgraph
> > filtering) is also related.
> >
>
> And this one once the above gets settled.
Another thing that could be interesting is a perf output mode that dumps
informations in the Kcachegrind format: http://kcachegrind.sourceforge.net/html/CallgrindFormat.html
so that Kcachegrind can open it.
next prev parent reply other threads:[~2012-07-06 7:40 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
2012-07-06 0:50 ` Arun Sharma
2012-07-06 1:28 ` Namhyung Kim
2012-07-06 7:40 ` Frederic Weisbecker [this message]
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=20120706074018.GA7728@somewhere.redhat.com \
--to=fweisbec@gmail.com \
--cc=acme@infradead.org \
--cc=asharma@fb.com \
--cc=bartoschek@gmx.de \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@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 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).