Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750986AbWIOA1e (ORCPT ); Thu, 14 Sep 2006 20:27:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932175AbWIOA1e (ORCPT ); Thu, 14 Sep 2006 20:27:34 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:42143 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S1750986AbWIOA1d (ORCPT ); Thu, 14 Sep 2006 20:27:33 -0400 Date: Fri, 15 Sep 2006 02:27:15 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Ingo Molnar cc: Daniel Walker , 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: <20060914234354.GA2754@elte.hu> Message-ID: References: <20060914171320.GB1105@elte.hu> <20060914181557.GA22469@elte.hu> <20060914202452.GA9252@elte.hu> <1158268113.17467.38.camel@c-67-180-230-165.hsd1.ca.comcast.net> <20060914221521.GA23371@elte.hu> <20060914234354.GA2754@elte.hu> 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: 1222 Lines: 29 Hi, On Fri, 15 Sep 2006, Ingo Molnar wrote: > int __trace function(char arg1, char arg2) > { > } > > where kprobes can be used to attach a lightweight tracepoint that does a > call, not a break (INT3) instruction. With static tracers we couldnt do > this so we'd have to stick with the static tracepoints forever! It's > always hard to remove features, so we have to make sure we add the > feature that we know is the best long-term solution. Where is the prove for that? Why can't the same rules apply to dynamic and static trace points? You're also mixing up function tracing with event tracing. Most of the LTT trace points log rather high level events, which are rather unlikely to disappear. It's more likely that the place where they are generated is moved and then it's only advantageous if the marker is moved as well at the same time. OTOH if the actual event really is not generated anymore, there is also no need for the marker anymore. 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/