> I did told you that it would be better you make PyTimeChart use the perf > scripting facilities, it handles all the above things + it would > avoid you to handle a lot of things. Actually, perf scripting facility is already supported by pytimechart but does not make it that easier to maintain. event name changes => must update, event fields added/removed => must update > > Now it's up to you, but don't count on us to make the ascii formatting > a stable ABI. I'm not against adding 1 line in pytimechart each time there is some change in ascii formatting > > >> actually, over all the events pytimechart supports, only power traces >> are stable... > > > Now one problem is that we have really broken the workqueue tracepoints > in this release. I thought nobody was using them so we could > refactor this tracepoint subsystem, my bad. No problem. I'll update pytimechart whenever someone sends me traces that does not work (I'm okay with pre 2.6.31 traces too...) Regards, Pierre -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
