From mboxrd@z Thu Jan 1 00:00:00 1970 From: fche@redhat.com (Frank Ch. Eigler) Subject: Re: [PATCH -tip v5 4/7] tracing: add kprobe-based event tracer Date: Mon, 11 May 2009 11:28:12 -0400 Message-ID: References: <20090509004829.5505.38720.stgit@localhost.localdomain> <20090509004859.5505.18729.stgit@localhost.localdomain> <20090511093224.GC23875@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Masami Hiramatsu , Ingo Molnar , Steven Rostedt , lkml , systemtap , kvm , Ananth N Mavinakayanahalli , Frederic Weisbecker , Tom Zanussi To: Christoph Hellwig Return-path: In-Reply-To: <20090511093224.GC23875@infradead.org> (Christoph Hellwig's message of "Mon, 11 May 2009 05:32:24 -0400") List-Unsubscribe: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org List-Id: kvm.vger.kernel.org Christoph Hellwig writes: > [...] But as with so many tracing bits in the kernel it's just > lowlevel bits without a good user interface. We'd really need some > high-level way for sysadmins/developers to use it. E.g. a version > of the systemtap compiler that doesn't build a kernel module but > instead uses the event tracer + the kprobes tracer. [...] This (the translator detecting that a particular script is simple enough to be executed in this manner) is theoretically possible. - FChE