On Thu, Oct 7, 2010 at 5:08 PM, Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx> wrote: > [ Adding a few more CCs, since this discussion is about a tracepoint > userspace ABI policy, which is a topic of general interest. ] To add a little more comment, this is not the first time that tracepoints ABI changes. You can look at pytimechart sourcecode: http://gitorious.org/pytimechart/pytimechart/blobs/master/timechart/ftrace.py from 2.6.31 which is the first kernel I support, sched_switch: 'task %s:%d [%d] ==> %s:%d [%d]', changed to: sched_switch: 'prev_comm=%s prev_pid=%d prev_prio=%d prev_state=%s ==> next_comm=%s next_pid=%d next_prio=%d', workqueue_execution: 'thread=%s func=%s\\+%s/%s','thread','func','func_offset','func_size'), changed to: workqueue_execution: 'thread=%s func=%s','thread','func'), actually, over all the events pytimechart supports, only power traces are stable... 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
