Re: Perf ABI versioning

From: Thomas Renninger
Date: Mon Jan 24 2011 - 16:49:08 EST

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 binaries which can be processed by userspace tools,
independent of the kernel version running below on which the
was produced.

Was just an idea, I agree that it's far away from being practical,
please ignore the thread...

Sorry for the noise,


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at