On Mon, Sep 06, 2010 at 04:13:57PM +0100, Stefan Hajnoczi wrote: > This patch series adds static tracing to QEMU. It can be used to instrument > QEMU code by means of lightweight logging called trace events. > > Prerna and I are now posting the entire patch series with a serious eye > towards > checking we meet users' and developers' tracing needs and with the goal of > getting this functionality merged into qemu.git.
The main question would be why create a tracing framework and probe markup macros specific to QEMU ? It looks like quite a few major open source projects (PostgreSQL, Python, TCL, OpenJDK) are using DTrace static probe markers for code instrumentation. IIUC this is accessible on Solaris, (Free/Net?)-BSD, OS-X and also Linux via SystemTAP's DTrace compat layer. Is this QEMU specific probe markup flexible enough to make it possible to also support DTrace/SystemTAP without having to add a second set of source code markers to every probe point ? Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
