Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751257AbWIORv0 (ORCPT ); Fri, 15 Sep 2006 13:51:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751278AbWIORv0 (ORCPT ); Fri, 15 Sep 2006 13:51:26 -0400 Received: from smtp.osdl.org ([65.172.181.4]:14534 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1751257AbWIORvY (ORCPT ); Fri, 15 Sep 2006 13:51:24 -0400 Date: Fri, 15 Sep 2006 10:49:55 -0700 From: Andrew Morton To: karim@opersys.com Cc: Alan Cox , Roman Zippel , Tim Bird , Ingo Molnar , Mathieu Desnoyers , linux-kernel@vger.kernel.org, Christoph Hellwig , Ingo Molnar , Greg Kroah-Hartman , Thomas Gleixner , Tom Zanussi , ltt-dev@shafik.org, Michel Dagenais Subject: Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108 Message-Id: <20060915104955.ad6c3622.akpm@osdl.org> In-Reply-To: <450ABF59.4010301@opersys.com> References: <20060914033826.GA2194@Krystal> <20060914112718.GA7065@elte.hu> <20060914135548.GA24393@elte.hu> <20060914171320.GB1105@elte.hu> <20060914181557.GA22469@elte.hu> <4509B03A.3070504@am.sony.com> <1158320406.29932.16.camel@localhost.localdomain> <1158323938.29932.23.camel@localhost.localdomain> <1158327696.29932.29.camel@localhost.localdomain> <1158331277.29932.66.camel@localhost.localdomain> <450ABA2A.9060406@opersys.com> <1158332324.29932.82.camel@localhost.localdomain> <450ABF59.4010301@opersys.com> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.6; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 894 Lines: 19 On Fri, 15 Sep 2006 10:57:29 -0400 Karim Yaghmour wrote: > But I submit to you that both explanations > actually highlight the argument I was making earlier with regards to > dynamic tracing (and gdb info in this case) actually require a non- > expert to chase kernel versions and create appropriate appropriate > scripts/config-info for the post-insertion of instrumentation > ... Again, I don't see this as a huge problem. patch(1) is able to keep track of specific places within source code even in the presence of quite violent changes to that source code. There's no reason why systemtap support code cannot do the same. - 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/