Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751415AbWIPKpp (ORCPT ); Sat, 16 Sep 2006 06:45:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751440AbWIPKpp (ORCPT ); Sat, 16 Sep 2006 06:45:45 -0400 Received: from omx1-ext.sgi.com ([192.48.179.11]:49841 "EHLO omx1.americas.sgi.com") by vger.kernel.org with ESMTP id S1751415AbWIPKpo (ORCPT ); Sat, 16 Sep 2006 06:45:44 -0400 Message-ID: <450BD5F4.10302@sgi.com> Date: Sat, 16 Sep 2006 12:46:12 +0200 From: Jes Sorensen User-Agent: Thunderbird 1.5.0.5 (X11/20060907) MIME-Version: 1.0 To: Chuck Ebbert <76306.1226@compuserve.com> Cc: Alan Cox , Greg Kroah-Hartman , linux-kernel , Roman Zippel , Paul Mundt , Karim Yaghmour , Ingo Molnar , Mathieu Desnoyers , Christoph Hellwig , Andrew Morton , Thomas Gleixner , Tom Zanussi , ltt-dev , Michel Dagenais Subject: Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108 References: <200609151316_MC3-1-CB57-4BE@compuserve.com> In-Reply-To: <200609151316_MC3-1-CB57-4BE@compuserve.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1400 Lines: 35 Chuck Ebbert wrote: > In-Reply-To: <1158331071.29932.63.camel@localhost.localdomain> > > On Fri, 15 Sep 2006 15:37:51 +0100, Alan Cox wrote: > >>> $ 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 >> Send patches. The fact nobody has them implemented on your platform >> isn't a reason to implement something else, quite the reverse in fact. > > Yes, but the point is: until that's done you can't claim kprobes is a > valid tracing tool for everyone. The fact that the remaining architectures haven't bothered implementing kprobe supposed should not be used as an argument for pushing something inferior out of laziness. It's the same with syscalls, the kernel infrastructure is there, but if you don't bother updating the syscall tables and wrap it in with glibc, then the call isn't available on your architecture. The core kprobe infrastructure is available to all architectures, it's up to the developers of the remaining architectures to implement the remaining bits. Jes - 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/