From: Milian Wolff <mail@milianw.de>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-perf-users@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: Reusable data analysis/parser library?
Date: Mon, 22 Jul 2013 19:33:30 +0200 [thread overview]
Message-ID: <8249514.rlupye1erJ@minime> (raw)
In-Reply-To: <20130722083311.GA12256@krava.brq.redhat.com>
On Monday 22 July 2013 10:33:11 Jiri Olsa wrote:
> On Sun, Jul 21, 2013 at 11:57:26PM +0200, Milian Wolff wrote:
> > On Thursday 27 December 2012 15:42:32 Milian Wolff wrote:
> > > Hey there,
> > >
> > > I found [1] and [2] but not a reusable shared library which one could
> > > use to write custom analyzers for perf.data files. Are you still
> > > working on this or should one rather stick to parsing the output of
> > > "perf script"?
> > >
> > > As a start I would like to integrate a parser into KCacheGrind to
> > > seamlessly open perf.data files with it.
> > >
> > > Thanks
> > >
> > > [1]: https://openlab-mu-internal.web.cern.ch/openlab-mu->
> > > internal/03_Documents/3_Technical_Documents/Technical_Reports/2011/Urs_
> > > Fassl er_report.pdf [2]:
> > > http://article.gmane.org/gmane.linux.kernel.perf.user/974/match=kcachegr
> > > ind
> >
> > Ping, is there anything available which I can use to write a perf.data
> > parser for KCacheGrind? This would be highly benefitial for many people
> > using perf.
> >
> > Otherwise, is there at least a solid documentation of the binary format
> > which I might then use to write a custom external library?
>
> hi,
> I'm currently doing some reorg in this part:
> http://marc.info/?l=linux-kernel&m=137408381902423&w=2
> I'll check and see if we could isolate the parser somehow.
This would be highly appreciated! Please keep me in touch when you decide
anything in that regard.
> Above patchset contains some doc of the perf.data format:
> http://marc.info/?l=linux-kernel&m=137408345402297&w=2
Ah, very interesting. Thank you! I'll try to look into it a bit.
> Also Andi sent out following python parser, but I did not
> get to it so far:
> http://marc.info/?l=linux-kernel&m=137424881921089&w=2
Thanks!
--
Milian Wolff
mail@milianw.de
http://milianw.de
prev parent reply other threads:[~2013-07-22 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 14:42 Reusable data analysis/parser library? Milian Wolff
2013-07-21 21:57 ` Milian Wolff
2013-07-22 8:33 ` Jiri Olsa
2013-07-22 17:33 ` Milian Wolff [this message]
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=8249514.rlupye1erJ@minime \
--to=mail@milianw.de \
--cc=ak@linux.intel.com \
--cc=jolsa@redhat.com \
--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 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).