Stefan Hajnoczi writes:
> On Sun, Aug 21, 2016 at 02:32:34PM +0200, Lluís Vilanova wrote:
>> Unfortuntely, I've been unable to to make dtrace recognise QEMU's events (I'm
>> only able to see the host kernel events). If someone with more experience on
>> it
>> can help me use dtrace with QEMU's events, I'll also add the supporting
>> library
>> to let dtrace do the callout to QEMU's moitor interface and control the
>> events,
>> and add a prperly useful example of that on the hypertrace docs (which was my
>> original intention).
> Which "dtrace" and host OS are you using?
> QEMU builds with static user-space probes. You need to tell DTrace or
> SystemTap to enable those probes in order to record trace data.
I'm using debian on a 4.6.0-1-amd64 kernel with systemtap 3.0.6.
I just gave it another try, and works if I use probes like:
process("<binary-path>").mark("<event-name>")
although they don't seem to appear on "stap -l" or anything like that (I cannot
find a "qemu" provider). But I'm still unable to print the event values. This:
probe
process("./install/vanilla/bin/qemu-system-i386").mark("guest_mem_before_exec")
{
printf("%p %lx %d\n", $arg1, $arg2, $arg3)
}
always prints "0x0 0x0 0", which is clearly wrong (other backend on the same
build print the correct values).
Also, I'm still not sure how to interact with QEMU's monitor interface from
within the probe code (probes execute in kernel mode, including "guru mode"
code).
If anybody can shed some like into any of this, I'd appreaciate it.
Cheers,
Lluis
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
