This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Qemu tracing
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Prerna Saxena <prerna at linux dot vnet dot ibm dot com>
- Cc: systemtap at sourceware dot org, Ananth <ananth at linux dot vnet dot ibm dot com>, Stefan Hajnoczi <stefanha at linux dot vnet dot ibm dot com>, Mahesh Jagannath Salgaonkar <mahesh at linux dot vnet dot ibm dot com>, Srikar Dronamraju <srikar at linux dot vnet dot ibm dot com>
- Date: Wed, 11 Aug 2010 12:18:59 -0400
- Subject: Re: Qemu tracing
- References: <4C611567.9030407@linux.vnet.ibm.com>
prerna wrote:
> Here's an update on a self contained userspace tracer mechanism I've
> been working on, for QEMU ; alongwith Stefan Hajnoczi.
Thank you!
> [...]
> To make guest tracing with QEMU truly independent of the host on which
> it runs, QEMU must be instrumented by self-contained tracer.
OK.
How did you choose the events (probe points) for tracing?
> When running QEMU on a linux host, one has the choice of using LTTnG
> as the supported backend for tracing. [...]
Using <sys/sdt.h> would be a natural second alternative for linux (and
dtrace platforms, if someone cares).
Even without that, have you tried applying normal systemtap user-space
probing to qemu to get some usability / performance impressions?
- FChE