Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755842Ab0AVCYZ (ORCPT ); Thu, 21 Jan 2010 21:24:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755630Ab0AVCYY (ORCPT ); Thu, 21 Jan 2010 21:24:24 -0500 Received: from mx1.redhat.com ([209.132.183.28]:19199 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755560Ab0AVCYX (ORCPT ); Thu, 21 Jan 2010 21:24:23 -0500 Date: Thu, 21 Jan 2010 21:22:55 -0500 From: "Frank Ch. Eigler" To: Linus Torvalds Cc: Andrew Morton , Stephen Rothwell , Ingo Molnar , Ananth N Mavinakayanahalli , Peter Zijlstra , Peter Zijlstra , Fr??d??ric Weisbecker , LKML , Steven Rostedt , Arnaldo Carvalho de Melo , linux-next@vger.kernel.org, "H. Peter Anvin" , utrace-devel@redhat.com, Thomas Gleixner Subject: Re: linux-next: add utrace tree Message-ID: <20100122022255.GF22003@redhat.com> References: <20100120062834.GB12165@elte.hu> <20100120072925.GA11395@elte.hu> <20100121013822.28781960.sfr@canb.auug.org.au> <20100122111747.3c224dfd.sfr@canb.auug.org.au> <20100121163004.8779bd69.akpm@linux-foundation.org> <20100121163145.7e958c3f.akpm@linux-foundation.org> <20100122005147.GD22003@redhat.com> <20100121170541.7425ff10.akpm@linux-foundation.org> <20100122012516.GE22003@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1711 Lines: 41 Hi - On Thu, Jan 21, 2010 at 05:32:47PM -0800, Linus Torvalds wrote: > [...] > > To the extent the discussion is colored by the new features enabled > > from this refactoring, well, there is Oleg's list which may or may not > > have mentioned enabling systemtap's user-space probing. > > Let's face it, system tap isn't going to be merged, so why even bring it > up? It was certainly not meant to derail the discussion about the merits of utrace as a useful cleanup API in its own right, but rather to be an example of what kinds of things become straightforward in its presence. You may be aware of nascent efforts to bring the same uprobes infrastructure to perf. > Every kernel developer I have _ever_ seen agrees that all the new > tracing is a million times superior. [...] And that is fine. We believe there is plenty of space in the problem domain for different approaches. > ... considering how little the system tap people ever did for the kernel. Less passionate analysis would identify a long history of contribution by the the greater affiliated team, including via merged code and by and passing on requirements and experiences. We have been trying to share as much as you have been willing to take. While systemtap's current codebase may not (and need not) have a future inside the kernel, chances are good that improvements in common infrastructure will allow systemtap to shrink and change enough that the question becomes moot. - 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/