From: Steven Rostedt <rostedt@goodmis.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
mingo@elte.hu, Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [patch] introduce TRACE_EVENT_ABI (was Re: TRACE_EVENT_ABI ?)
Date: Wed, 23 Sep 2009 10:03:52 -0400 [thread overview]
Message-ID: <1253714632.4498.3.camel@frodo> (raw)
In-Reply-To: <20090923124340.GA6093@infradead.org>
On Wed, 2009-09-23 at 08:43 -0400, Christoph Hellwig wrote:
> I'm not sure we can support any as an ABI yet. The text format seems to
> volatile in general - not just the output of the individual trace events
> but also the common file format, and for the binary format we need to
> figure a good way to tag the output yet. Also when we define one as
> one ABI we should make very clear what that means, e.g. does it have to stay
> exactly as is? Or can we add new fields but not remove old one?
I had this discussion with people in Portland. We seem to agree that
this should just lock the old fields in, but you can add new ones at the
end.
-- Steve
next prev parent reply other threads:[~2009-09-23 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 12:43 [patch] introduce TRACE_EVENT_ABI (was Re: TRACE_EVENT_ABI ?) Christoph Hellwig
2009-09-23 14:03 ` Steven Rostedt [this message]
2009-09-23 14:07 ` Christoph Hellwig
2009-09-23 15:38 ` Ingo Molnar
2009-09-23 16:16 ` Mathieu Desnoyers
-- strict thread matches above, loose matches on Subject: below --
2009-09-21 7:36 TRACE_EVENT_ABI ? Arjan van de Ven
2009-09-21 13:26 ` Steven Rostedt
2009-09-21 13:28 ` Arjan van de Ven
2009-09-21 16:46 ` Steven Rostedt
2009-09-21 18:00 ` Arjan van de Ven
2009-09-21 21:20 ` Steven Rostedt
2009-09-23 8:32 ` [patch] introduce TRACE_EVENT_ABI (was Re: TRACE_EVENT_ABI ?) Arjan van de Ven
2009-09-23 10:57 ` Frédéric 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=1253714632.4498.3.camel@frodo \
--to=rostedt@goodmis.org \
--cc=arjan@infradead.org \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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