Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751475AbWIOODr (ORCPT ); Fri, 15 Sep 2006 10:03:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751482AbWIOODr (ORCPT ); Fri, 15 Sep 2006 10:03:47 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:22437 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S1751475AbWIOODq (ORCPT ); Fri, 15 Sep 2006 10:03:46 -0400 Date: Fri, 15 Sep 2006 16:03:24 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Jes Sorensen cc: Paul Mundt , Karim Yaghmour , Ingo Molnar , Mathieu Desnoyers , linux-kernel@vger.kernel.org, Christoph Hellwig , Andrew Morton , 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 In-Reply-To: <450AAE39.4040205@sgi.com> Message-ID: References: <20060914112718.GA7065@elte.hu> <20060914135548.GA24393@elte.hu> <20060914171320.GB1105@elte.hu> <20060914181557.GA22469@elte.hu> <4509A54C.1050905@opersys.com> <450A9EC9.9080307@opersys.com> <20060915132052.GA7843@localhost.usen.ad.jp> <450AAE39.4040205@sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1580 Lines: 41 Hi, On Fri, 15 Sep 2006, Jes Sorensen wrote: > Roman Zippel wrote: > > The claim that these tracepoints would be maintainance burden is pretty > > much unproven so far. The static tracepoint haters just assume the kernel > > will be littered with thousands of unrelated tracepoints, where a good > > tracepoint would only document what already happens in that function, so > > that the tracepoint would be far from something obscure, which only few > > people could understand and maintain. > > How do you propose to handle the case where two tracepoint clients wants > slightly different data from the same function? I saw this with LTT > users where someone wanted things in different places in schedule(). > > It *is* a nightmare to maintain. That nightmare would not be with tracepoints itself, but with the users of it, so you're missing the point. Tracepoints can be abused of course, but it's quite a leap to conclude from this that they are bad in general. > You still haven't explained your argument about kprobes not being > generally available - where? Huh? What kind of explanation do you want? $ grep KPROBES arch/*/Kconf* arch/i386/Kconfig:config KPROBES arch/ia64/Kconfig:config KPROBES arch/powerpc/Kconfig:config KPROBES arch/sparc64/Kconfig:config KPROBES arch/x86_64/Kconfig:config KPROBES bye, Roman - 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/