[PATCH -tip 0/6 V4] tracing: kprobe-based event tracer

[Andi Kleen]

> 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.