From: "Daniel P. Berrange" <berrange@redhat.com>
To: Prerna Saxena <prerna@linux.vnet.ibm.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 09:44:13 +0100 [thread overview]
Message-ID: <20101027084413.GE30971@redhat.com> (raw)
In-Reply-To: <4CC7CD32.3040906@linux.vnet.ibm.com>
On Wed, Oct 27, 2010 at 12:26:50PM +0530, Prerna Saxena wrote:
> 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") { .. }
Yes, that's doable. The other problem with this tapset is that it
only works for the 'qemu' binary and not the 'qemu-system-XXXX'
binaries. I either need to make the probe cover all binaries, or
generate one tapset per architecture target. I'm going to split
this patch in 2, one with just the core dtrace bits, and a second
with the systemtap tapset addon.
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 :|
prev parent reply other threads:[~2010-10-27 8:44 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
2010-10-27 8:44 ` Daniel P. Berrange [this message]
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=20101027084413.GE30971@redhat.com \
--to=berrange@redhat.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=mahesh@linux.vnet.ibm.com \
--cc=prerna@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.