Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751072AbWISPWz (ORCPT ); Tue, 19 Sep 2006 11:22:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750947AbWISPWz (ORCPT ); Tue, 19 Sep 2006 11:22:55 -0400 Received: from mx1.redhat.com ([66.187.233.31]:37823 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S1750806AbWISPWy (ORCPT ); Tue, 19 Sep 2006 11:22:54 -0400 To: Mathieu Desnoyers Cc: Paul Mundt , linux-kernel , Jes Sorensen , Andrew Morton , Tom Zanussi , Richard J Moore , Michel Dagenais , Christoph Hellwig , Greg Kroah-Hartman , Thomas Gleixner , William Cohen , "Martin J. Bligh" , Ingo Molnar , ltt-dev@shafik.org, systemtap@sources.redhat.com Subject: Re: [PATCH] Linux Kernel Markers References: <20060918234502.GA197@Krystal> From: fche@redhat.com (Frank Ch. Eigler) Date: 19 Sep 2006 11:21:43 -0400 In-Reply-To: <20060918234502.GA197@Krystal> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.3 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: 869 Lines: 15 Mathieu Desnoyers writes: > [...] I take for agreed that both static and dynamic tracing are > useful for different needs and that a full markup must support both > and combinations, letting the user or the distribution choose. Elaborating on Ingo's "one mechanism" comments, I believe a marker widget needs to be generic at run time. We're not just looking for a way of hiding direct calls to lttng in a marker macro. We're looking for a way of marking spots & data in a uniform way, then later (run-time) binding each of those markers to (tools such as) lttng and/or systemtap. - FChE - 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/