On Mon, Jan 24, 2011 at 5:04 PM, Thomas Renninger <trenn@xxxxxxx> wrote:
> Hi,
>
> as I recently cleaned up the power events with
> some format/abi adjustings...
>
> I realized that it was rather easy to adjust
> the stuff in drivers/tools/perf, because there
> are some nice facilities to query which events
> are available.
>
> I looked at pytimechart, there it's not that nice
> and convenient would be some kind of version number.
pytimechart does pattern matching to be able to work with different
version of the ftrace formats.
For a same trace type, it will try different trace format, until it
finds a match.
e.g.:
('irq_handler_entry', 'irq=%d handler=%s','irq','name'),
('irq_handler_entry', 'irq=%d name=%s','irq','name'),
The problem of this approach is obviously that you have to modify
pytimechart each time there is a new format, it cannot just look at
the trace format and just ignore new fields that it dont care of.
Please also note, that pytimechart also have a perf-python backend
that may not have such issues in dealing with new events fields, but
is actually sensible to event fields renaming.
> Would it make sense to introduce a trace
> ABI version number?
So as soon as pytimechart is the only user of this versionning, I'm
not sure it is really needed.
Regards,
Pierre
--
To unsubscribe from this list: send the line "unsubscribe linux-trace-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
|