On Sat, 2010-10-09 at 21:39 -0400, Steven Rostedt wrote: > I've been hesitant in the pass from doing the TRACE_EVENT_ABI() > before, because Peter Zijlstra (who is currently MIA) has been strongly > against it. I see no point in the TRACE_EVENT_ABI() because if I need to change such a tracepoint to reflect changes in the kernel then I will freely do so. Even seemingly stable points like sched_switch(), which we all agree will stay around forever (gotta have context switches on a multi-tasking OS) will not stay stable when we add/change scheduling policies. Sure, the prev and next task thing will stay the same, but the meaning and interpretation of things like the prio field will not, esp when we go add something like a deadline scheduler that isn't priority based. So one possibility is to simply remove all that information from the tracepoints, remove the prio and state fields, but how useful is that? I guess what I'm saying is that even if we were to provide _ABI I see us getting into this very same argument over and over again, making me want to remove all this trace event muck right now before it gets worse. -- 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
