On Tue, 2010-09-21 at 14:33 +0100, Stefan Hajnoczi wrote:
net.c qemu_deliver_packet(), etc - network statistics
Yes.
Further digging into the code in the net/ directory, there are more
functions that should be traced/probed - e.g. a lot of the net_socket*
routines.
Given that SystemTap,
On Wed, 2010-09-22 at 13:33 +0100, Stefan Hajnoczi wrote:
KVM does not generate code. Almost all the emulation code in the
source tree is part of the Tiny Code Generator (TCG) used when KVM is
not enabled (e.g. to emulate an ARM board on an x86-64 host).
Thanks, that's what I thought too.
On Mon, 2010-09-20 at 14:36 +0100, Stefan Hajnoczi wrote:
Right now there are few pre-defined probes (trace events in QEMU
tracing speak). As I develop I try to be mindful of new ones I create
and whether they would be generally useful. I intend to contribute
more probes and hope others will
On Wed, 2010-09-08 at 15:08 +0100, Stefan Hajnoczi wrote:
Hi Rayson,
For the KVM kernel module Linux trace events are already used. For
example, see arch/x86/kvm/trace.h and check out
/sys/kernel/debug/tracing/events/kvm/*. There is a set of useful
static trace points for vm_exit/vm_enter,
Hi all,
I am a developer of Systemtap. I am looking into tracing KVM (the kernel
part and QEMU) and also the KVM guests with Systemtap. I googled and
found references to Xenprobes and xdt+dtrace, and I was wondering if
someone is working on the dynamic tracing interface for KVM?
I've read the
