From: Milian Wolff <mail@milianw.de>
To: linux-perf-users@vger.kernel.org
Subject: Reusable data analysis/parser library?
Date: Thu, 27 Dec 2012 15:42:32 +0100 [thread overview]
Message-ID: <1435472.kqSja2FelP@minime> (raw)
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
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_Fassler_report.pdf
[2]:
http://article.gmane.org/gmane.linux.kernel.perf.user/974/match=kcachegrind
--
Milian Wolff
mail@milianw.de
http://milianw.de
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2012-12-27 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 14:42 Milian Wolff [this message]
2013-07-21 21:57 ` Reusable data analysis/parser library? Milian Wolff
2013-07-22 8:33 ` Jiri Olsa
2013-07-22 17:33 ` Milian Wolff
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=1435472.kqSja2FelP@minime \
--to=mail@milianw.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 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).