Em Mon, Jan 24, 2011 at 10:49:13PM +0100, Thomas Renninger escreveu: > On Monday 24 January 2011 22:28:38 Ingo Molnar wrote: > > * Frederic Weisbecker <fweisbec@xxxxxxxxx> wrote: > > > > > This may be generally useful to help dealing with tracepoint ABI changes. > > > > > > But instead of a global tracing ABI number, I would rather suggest one number per > > > tracepoint subsystem (sched, power, etc...). > > > > Nooooooooooo ... !!! :-) > > > > Please lets stop this madness before it gets too serious: we dont do ABI version > > numbering in Linux, full stop. > Ok... :) > > > We use 'natural' ABIs where the lack of an ABI component triggers some sort of > > clean, finegrained error. Like a -EINVAL on a not-yet-implemented ABI component, a > > non-existent file entry, or -ENOSYS on a non-existent syscall. > If the whole stuff matures, someone might think about a nice concept to be able > to shift around perf.data binaries which can be processed by userspace tools, > independent of the kernel version running below on which the perf.data > was produced. We try to do that already, things like sample_id_all that is a feature present on a new kernel are capability queried by trying to ask the kernel for it and if it fails, cope with that and do as before it, in some cases warning the user if the fallback can lead to inacuracies. Shifting around perf.data files accross arquitectures and OS/vendor releases is an everyday goal. I.e. the new perf binary works with older kernels. We also try hard to keep the latest tools building on older kernels. Using the /format file hashed as peterz said is elegant, fine grained content based ABI number :-) - Arnaldo -- 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
|