This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [PATCH -tip 0/6 V4] tracing: kprobe-based event tracer
- From: Andi Kleen <andi at firstfloor dot org>
- To: Ingo Molnar <mingo at elte dot hu>
- Cc: Avi Kivity <avi at redhat dot com>, Masami Hiramatsu <mhiramat at redhat dot com>, "H. Peter Anvin" <hpa at zytor dot com>, Frederic Weisbecker <fweisbec at gmail dot com>, Steven Rostedt <rostedt at goodmis dot org>, Ananth N Mavinakayanahalli <ananth at in dot ibm dot com>, Andrew Morton <akpm at linux-foundation dot org>, Andi Kleen <andi at firstfloor dot org>, Jim Keniston <jkenisto at us dot ibm dot com>, kvm at vger dot kernel dot org, systemtap-ml <systemtap at sources dot redhat dot com>, LKML <linux-kernel at vger dot kernel dot org>
- Date: Fri, 3 Apr 2009 14:25:39 +0200
- Subject: Re: [PATCH -tip 0/6 V4] tracing: kprobe-based event tracer
- References: <49D4F4B5.9040107@redhat.com> <20090403112639.GC31399@elte.hu> <49D5F80B.7000305@redhat.com> <20090403121202.GI31399@elte.hu>
> So ... we can do the library decoder for kprobes purposes, and
> someone versed in the KVM emulator can then combine the two.
The KVM (or rather Xen, that is where it comes from) decoder is already
a "library decoder". That is it does nearly everything
through callbacks, and if you don't want some functionality
you can nop the callbacks. Nearly because some some
direct KVM references have crept in recently (e.g. to vcpus),
but those could be probably removed again without too much effort.
There are not many of them.
Also doing another interpreter is a lot of work and a lot of testing,
so basing it on something that is already well tested is probably
a good idea.
-/dev/null/Andi
--
ak@linux.intel.com -- Speaking for myself only.