From mboxrd@z Thu Jan 1 00:00:00 1970 From: Masami Hiramatsu Subject: Re: [PATCH -tip v8 7/7] tracing: add kprobe-based event tracer Date: Sat, 30 May 2009 10:38:50 -0400 Message-ID: <4A2144FA.6080508@redhat.com> References: <20090529000326.17532.70868.stgit@localhost.localdomain> <20090529000353.17532.71995.stgit@localhost.localdomain> <20090530081526.GC15755@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Ingo Molnar , Steven Rostedt , lkml , systemtap , kvm , DLE , Ananth N Mavinakayanahalli , Frederic Weisbecker , Tom Zanussi To: Christoph Hellwig Return-path: In-Reply-To: <20090530081526.GC15755@infradead.org> List-Unsubscribe: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org List-Id: kvm.vger.kernel.org Christoph Hellwig wrote: > On Thu, May 28, 2009 at 08:03:53PM -0400, Masami Hiramatsu wrote: >> Add kprobes-based event tracer on ftrace. > > Wouldn't it make more sense to call this the dynamic event tracer? > > The use of kprobes is more an implementation detail than something > the user cares about. Hmm, I don't think so, because other tracers (e.g. hw breakpoint tracer) can also add their events dynamically by trace_add/remove_event_call. It's more flexible than this tracer includes those events. Thank you, -- Masami Hiramatsu Software Engineer Hitachi Computer Products (America) Inc. Software Solutions Division e-mail: mhiramat@redhat.com