From: Peter Zijlstra <a.p.zijlstra@chello.nl>
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>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Perf ABI versioning
Date: Mon, 24 Jan 2011 21:39:03 +0100 [thread overview]
Message-ID: <1295901543.28776.475.camel@laptop> (raw)
In-Reply-To: <20110124203449.GC2318@nowhere>
On Mon, 2011-01-24 at 21:34 +0100, Frederic Weisbecker wrote:
>
> But instead of a global tracing ABI number, I would rather suggest
> one number per tracepoint subsystem (sched, power, etc...).
>
> Ideally it would be per event, but sometimes those events tend to be
> renamed or a whole tracepoint subsystem refactored (see workqueue
> lately). Hence it might be better per subsystem.
What's wrong with what we have? the /format file is pretty unique to
function as a version number of you use a hash over it.
next prev parent reply other threads:[~2011-01-24 20:38 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 [this message]
2011-01-24 20:40 ` Frederic Weisbecker
2011-01-24 21:28 ` Ingo Molnar
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=1295901543.28776.475.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--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=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tardyp@gmail.com \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.