From: Arun Sharma <asharma@fb.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Christoph Bartoschek <bartoschek@gmx.de>,
linux-perf-users@vger.kernel.org
Subject: Stand alone perf.data parser (Was Re: Callgraph like kcachegrind)
Date: Fri, 6 Jul 2012 07:58:07 -0700 [thread overview]
Message-ID: <4FF6FCFF.5070400@fb.com> (raw)
In-Reply-To: <20120706074018.GA7728@somewhere.redhat.com>
On 7/6/12 12:40 AM, Frederic Weisbecker wrote:
> 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.
I spent a night couple of months ago hacking on this:
https://github.com/adsharma/py-perf-parser
It needs to be combined with code that can symbolize raw IP addresses to
make it more useful (pydevtools, pyelftools or parts of perf exported as
a library)
Thought I'd post it here, so folks interested in transforming perf.data
into something else can hack on it.
-Arun
next prev parent reply other threads:[~2012-07-06 14:58 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
2012-07-06 14:58 ` Arun Sharma [this message]
2012-07-06 15:12 ` Stand alone perf.data parser (Was Re: Callgraph like kcachegrind) 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=4FF6FCFF.5070400@fb.com \
--to=asharma@fb.com \
--cc=acme@infradead.org \
--cc=bartoschek@gmx.de \
--cc=fweisbec@gmail.com \
--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 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.