From: Prerna Saxena <prerna@linux.vnet.ibm.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>,
Ananth <ananth@linux.vnet.ibm.com>,
qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2] Add a DTrace tracing backend targetted for SystemTAP compatability
Date: Wed, 27 Oct 2010 12:26:50 +0530 [thread overview]
Message-ID: <4CC7CD32.3040906@linux.vnet.ibm.com> (raw)
In-Reply-To: <1287583790-9349-1-git-send-email-berrange@redhat.com>
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
next prev parent reply other threads:[~2010-10-27 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 14:09 [Qemu-devel] [PATCH v2] Add a DTrace tracing backend targetted for SystemTAP compatability Daniel P. Berrange
2010-10-20 14:36 ` Stefan Hajnoczi
2010-10-27 6:56 ` Prerna Saxena [this message]
2010-10-27 8:44 ` Daniel P. Berrange
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CC7CD32.3040906@linux.vnet.ibm.com \
--to=prerna@linux.vnet.ibm.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=berrange@redhat.com \
--cc=mahesh@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).