From: Sripathi Kodi <sripathik@in.ibm.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Prerna Saxena <prerna@linux.vnet.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Reg. trace infrastructure
Date: Mon, 5 Jul 2010 22:39:19 +0530 [thread overview]
Message-ID: <20100705223919.324fdf4a@in.ibm.com> (raw)
Hi Stefan, Prerna,
I pulled down QEMU tracing code from git://repo.or.cz/qemu/stefanha.git
and tried to use it to trace something in virtio-9p code. I don't have
any knowledge of how traces are implemented and I just went with the
documentation. With help from Prerna, I was able to insert a trace
point and observe it getting hit from the QEMU monitor. However, I have
a few questions about this. Could you please help me out?
*) My understanding is the traces are dumped to a file only when the
trace buffer gets filled. Is there a way to:
a) Forcibly dump the contents of the buffer when needed.
b) When QEMU exits it should dump the buffer. Doesn't seem to be
doing this now.
c) A way to specify the file into which it writes the traces.
*) Is QEMU monitor the only way to enable/disable trace points? Is it
possible to programmatically enable/disable trace points from within
QEMU code? If that is not possible, is it possible to specify all trace
points to be enabled in a text file and ask QEMU to read the file when
it starts up?
*) Is it possible to enable/disable a bunch of trace points at one
shot? Can trace points be grouped in some way? Can I say "enable all
trace points in a particular .c file" or "enable all trace points in
these 2 functions"?
Thanks a lot for your help.
-Sripathi.
next reply other threads:[~2010-07-05 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 17:09 Sripathi Kodi [this message]
2010-07-06 12:45 ` [Qemu-devel] Re: Reg. trace infrastructure Stefan Hajnoczi
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=20100705223919.324fdf4a@in.ibm.com \
--to=sripathik@in.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 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).