Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751867Ab1EJEo7 (ORCPT ); Tue, 10 May 2011 00:44:59 -0400 Received: from ipmail07.adl2.internode.on.net ([150.101.137.131]:45616 "EHLO ipmail07.adl2.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750870Ab1EJEo6 (ORCPT ); Tue, 10 May 2011 00:44:58 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AosEAG3CyE15LBzagWdsb2JhbACmAhUBARYmJcVODoYABJ5d Date: Tue, 10 May 2011 14:44:38 +1000 From: Dave Chinner To: Steven Rostedt Cc: Ingo Molnar , David Sharp , Vaibhav Nagarnaik , Michael Rubin , Linus Torvalds , Arjan van de Ven , linux-kernel , Frederic Weisbecker , Peter Zijlstra , Thomas Gleixner , Christoph Hellwig , Arnd Bergmann Subject: Re: Fix powerTOP regression with 2.6.39-rc5 Message-ID: <20110510044438.GB19446@dastard> References: <4DC45537.6070609@linux.intel.com> <1304713252.25414.2532.camel@gandalf.stny.rr.com> <20110507065803.GA23414@elte.hu> <1304765110.25414.2564.camel@gandalf.stny.rr.com> <20110507144402.GC2859@elte.hu> <1304788829.11129.57.camel@frodo> <20110507190033.GA11465@elte.hu> <1304996847.2969.151.camel@frodo> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1304996847.2969.151.camel@frodo> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1749 Lines: 43 On Mon, May 09, 2011 at 11:07:27PM -0400, Steven Rostedt wrote: > > Nor do you really seem to see the problem that changing tracepoints > > brings with itself. > > I am not for changing tracepoints on a whim. But I would like > tracepoints to change as the kernel design changes. The reason > tracepoints have currently been stable is that kernel design changes do > not happen often. But they do happen, and I foresee that in the future, > the kernel will have a large number of "legacy tracepoints", and we will > be stuck maintaining them forever. > > What happens if someone designs a tool that analyzes the XFS > filesystem's 200+ tracepoints? Will all those tracepoints now become > ABI? That's crazy talk. XFS tracepoints are _not ever_ guaranteed to be consistent from one kernel to another - they are highly dependent on the implementation of the code, and as such will change *without warning*. This has been the case for the XFS event subsystem since back in the days of Irix (yes, that's where most of the events were originally implemented). The fact that they are now exported via TRACE_EVENT() (so no kernel debugger is needed) does not change the fact the information is really for developer use only and as such are volatile.... So, if someone wants to write an application that parses the XFS tracepoints directly, then they have to live with the fact that tracepoints will come and go and change size and shape all the time. Cheers, Dave. -- Dave Chinner david@fromorbit.com -- 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/