From: Prerna Saxena <prerna@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Maneesh Soni <maneesh@linux.vnet.ibm.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Ananth <ananth@linux.vnet.ibm.com>,
qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC 0/3] Tracing framework for QEMU
Date: Tue, 08 Jun 2010 14:05:54 +0530 [thread overview]
Message-ID: <4C0E00EA.40801@linux.vnet.ibm.com> (raw)
In-Reply-To: <AANLkTilRugnJaXjvHTS8P4KNMIYsVqLp4yhwbbTAZdA_@mail.gmail.com>
Hi Stefan,
> Interesting to see your patches, tracepoint definitions/declarations
> look similar to in-kernel tracepoints :).
The choice of a kernel-tracepoint approach had advantages since it
places no inherent limitation on maximum number of arguments that can be
logged. Also, it is flexible enough to dump entire arrays if need be --
which is not as easily accomplished in the proposed approach as with
kernel tracepoints.
--
Prerna Saxena
Linux Technology Centre,
IBM Systems and Technology Lab,
Bangalore, India
prev parent reply other threads:[~2010-06-08 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 16:05 [Qemu-devel] [RFC 0/3] Tracing framework for QEMU Prerna Saxena
2010-05-24 16:15 ` [Qemu-devel] [PATCH 1/3]make tdb_hash available Prerna Saxena
2010-05-24 16:16 ` [Qemu-devel] [PATCH 2/3] Tracepoint, buffer & monitor framework Prerna Saxena
2010-05-25 11:40 ` Stefan Hajnoczi
2010-05-25 18:20 ` Prerna Saxena
2010-05-25 20:07 ` Stefan Hajnoczi
2010-05-24 16:19 ` [Qemu-devel] [PATCH 3/3] Samples to add a tracepoint Prerna Saxena
2010-05-25 11:38 ` Stefan Hajnoczi
2010-05-25 11:43 ` [Qemu-devel] [RFC 0/3] Tracing framework for QEMU Stefan Hajnoczi
2010-06-08 8:35 ` Prerna Saxena [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=4C0E00EA.40801@linux.vnet.ibm.com \
--to=prerna@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=maneesh@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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).