From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Thomas Renninger <trenn@suse.de>,
tardyp@gmail.com, jean.pihet@newoldbits.com,
acme@ghostprotocols.net, linux-perf-users@vger.kernel.org,
mathieu.desnoyers@efficios.com,
linux-trace-users@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Perf ABI versioning
Date: Mon, 24 Jan 2011 22:28:38 +0100 [thread overview]
Message-ID: <20110124212838.GB13724@elte.hu> (raw)
In-Reply-To: <20110124203449.GC2318@nowhere>
* Frederic Weisbecker <fweisbec@gmail.com> 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.
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.
Such a design is arbitrarily backportable or forward portable, it's extensible and
it is actually maintainable.
In the ABI version numbering direction lies Windows madness ...
Thanks,
Ingo
next prev parent reply other threads:[~2011-01-24 21:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 16:04 Perf ABI versioning Thomas Renninger
2011-01-24 16:18 ` Thomas Renninger
2011-01-24 17:26 ` Pierre Tardy
2011-01-24 17:28 ` Jean Pihet
2011-01-24 20:05 ` Frederic Weisbecker
2011-01-24 20:12 ` Mathieu Desnoyers
2011-01-24 21:02 ` Thomas Renninger
2011-01-24 20:34 ` Frederic Weisbecker
2011-01-24 20:39 ` Peter Zijlstra
2011-01-24 20:40 ` Frederic Weisbecker
2011-01-24 21:28 ` Ingo Molnar [this message]
2011-01-24 21:49 ` Thomas Renninger
2011-01-24 21:57 ` Arnaldo Carvalho de Melo
2011-01-24 22:30 ` Thomas Renninger
2011-01-24 22:46 ` Frederic Weisbecker
2011-01-24 23:05 ` Arnaldo Carvalho de Melo
2011-01-24 21:59 ` Frederic Weisbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110124212838.GB13724@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=tardyp@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=trenn@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).