Date: Mon, 21 Sep 2009 15:28:53 +0200
From: Arjan van de Ven <arjan@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Frederic Weisbecker <fweisbec@gmail.com>,
       mingo@elte.hu
Subject: Re: TRACE_EVENT_ABI ?
Message-ID: <20090921152853.2f8c0597@infradead.org>
In-Reply-To: <alpine.DEB.2.00.0909210926010.7647@gandalf.stny.rr.com>
References: <20090921093652.0722d745@infradead.org>
	<alpine.DEB.2.00.0909210926010.7647@gandalf.stny.rr.com>
Organization: Intel
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1316
Lines: 41

On Mon, 21 Sep 2009 09:26:41 -0400 (EDT)
Steven Rostedt <rostedt@goodmis.org> wrote:

> 
> [ Resending due to wrong SMTP server ]
> 
> 
> On Mon, 21 Sep 2009, Arjan van de Ven wrote:
> 
> > Hi,
> > 
> > Ingo suggested to make a TRACE_EVENT_ABI, which is equivalent in
> > implementation to TRACE_EVENT, except that it signals a stable
> > interface.
> > 
> > In trying to implement this I'm running into a wall where
> > TRACE_EVENT keeps being defined in many different ways all over the
> > place, making this a really nasty hack to make it just an alias.
> > 
> > Do you have any clever ideas on how to make this an alias without
> > fouling up the whole tracing system?
> > 
> 
> I don't know what you've done so far, but can't you simply in
> tracepoint.h define:
> 
> #define TRACE_EVENT_API(a,b,c,d,e) TRACE_EVENT(a,b,c,d,e)

unfortunately, due to the preprocessor trickery around TRACE_EVENT this
completely barfs.


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/