From: Prerna Saxena <prerna@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Mahesh <mahesh@linux.vnet.ibm.com>,
Ananth Narayan <ananth@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [Tracing][PATCH 0/2] More Trace events
Date: Wed, 11 Aug 2010 17:13:53 +0530 [thread overview]
Message-ID: <20100811171353.7d84bdbc@zephyr> (raw)
In-Reply-To: <20100811101427.GA2262@stefan-thinkpad.transitives.com>
Set of patches to add trace-events for tracking IO and balloon events
flagged via the monitor.
--
Prerna Saxena
Linux Technology Centre,
IBM Systems and Technology Lab,
Bangalore, India
next prev parent reply other threads:[~2010-08-11 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 8:25 [Qemu-devel] [Tracing] More Trace events Prerna Saxena
2010-08-11 10:14 ` [Qemu-devel] " Stefan Hajnoczi
2010-08-11 11:43 ` Prerna Saxena [this message]
2010-08-11 14:27 ` [Qemu-devel] [Tracing][PATCH 0/2] " Stefan Hajnoczi
2010-08-11 11:45 ` [Qemu-devel] [Tracing][PATCH 1/2] " Prerna Saxena
2010-08-11 11:46 ` [Qemu-devel] [Tracing][PATCH 2/2] " Prerna Saxena
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=20100811171353.7d84bdbc@zephyr \
--to=prerna@linux.vnet.ibm.com \
--cc=ananth@linux.vnet.ibm.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).