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=kcachegrind > > 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. Above patchset contains some doc of the perf.data format: http://marc.info/?l=linux-kernel&m=137408345402297&w=2 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 jirka -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
