qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2] Add a DTrace tracing backend targetted for S


From: Prerna Saxena
Subject: Re: [Qemu-devel] [PATCH v2] Add a DTrace tracing backend targetted for SystemTAP compatability
Date: Wed, 27 Oct 2010 12:26:50 +0530
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.9) Gecko/20100921 Fedora/3.1.4-1.fc13 Thunderbird/3.1.4

ACK, works well!
A suggestion though..

On 10/20/2010 07:39 PM, Daniel P. Berrange wrote:

eg, instead of

   probe process("qemu").mark("qemu_malloc") {
     printf("Malloc %d %p\n", $arg1, $arg2);
   }

The addition of qemu.stp to /usr/share/systemtap/tapset/
lets users write

   probe qemu.qemu_malloc {
     printf("Malloc %d %p\n", size, ptr);
   }
...


diff --git a/tracetool b/tracetool
index 7010858..047f16b 100755
--- a/tracetool
+++ b/tracetool
+linetos_dtrace()
+{
+    local name args arglist state
+
+    # Define prototype for probe arguments
+    cat<<EOF
+probe qemu.$name = process("qemu").mark("$name")
+{

The 'process' probes only work by looking for the binary in $PATH, unless the full path is specified. When compiling qemu in non-standard locations ( ie with --prefix), such probes would not point to the correct binary. It could be nice if tracetool could pass the full build path for defining the probe point. Eg,

probe qemu.qemu_malloc = process("/Path/to/build/dir/bin/qemu").mark("qemu_malloc") { .. }

--
Prerna Saxena

Linux Technology Centre,
IBM Systems and Technology Lab,
Bangalore, India



reply via email to

[Prev in Thread] Current Thread [Next in Thread]