Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751370AbWIOSKX (ORCPT ); Fri, 15 Sep 2006 14:10:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751356AbWIOSKW (ORCPT ); Fri, 15 Sep 2006 14:10:22 -0400 Received: from opersys.com ([64.40.108.71]:58121 "EHLO www.opersys.com") by vger.kernel.org with ESMTP id S1751344AbWIOSKU (ORCPT ); Fri, 15 Sep 2006 14:10:20 -0400 Message-ID: <450AEEEB.6040005@opersys.com> Date: Fri, 15 Sep 2006 14:20:27 -0400 From: Karim Yaghmour Reply-To: karim@opersys.com Organization: Opersys inc. User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.6) Gecko/20060804 Fedora/1.0.4-0.5.1.fc5 SeaMonkey/1.0.4 MIME-Version: 1.0 To: Andrew Morton 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 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> <20060915104955.ad6c3622.akpm@osdl.org> In-Reply-To: <20060915104955.ad6c3622.akpm@osdl.org> 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: 910 Lines: 21 Andrew Morton wrote: > 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. If you don't want to listen to my part of the argument then consider the point of view of those who have maintained systems entirely based on binary editing, namely systemtap and LKET. It's indicative that all those who have been involved in tracing, be it by static instrumentation of code or the use of binary editing, all favor some form of static markup mechanism of the code. Karim - 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/