From: Luis Useche <luis@cs.fiu.edu>
To: Sami Kiminki <sami.kiminki@tkk.fi>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] POLL: Support for instrumentation?
Date: Thu, 18 Jun 2009 12:00:30 -0400 [thread overview]
Message-ID: <20090618160030.GA7744@meg.local> (raw)
In-Reply-To: <1245336842.32163.18.camel@dis>
On Thu, Jun 18, 2009 at 05:54:02PM +0300, Sami Kiminki wrote:
> We are considering doing some work on instrumentation support for QEMU.
> But before rushing into implementation, I wonder if there is more
> general interest in this subject, and if so, what kind of
> instrumentation would you like to see?
I have been trying to instrument qemu code to get the traces of memory
accesses. I have seen several threads in this mail list talking about this
topic so probably it will be well received.
Bochs provides an instrumentation utility that you can probably look to
get some ideas.
Best,
--
Luis Useche <luis@cs.fiu.edu>
Ph.D. Student
Florida International University
next prev parent reply other threads:[~2009-06-18 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 14:54 [Qemu-devel] POLL: Support for instrumentation? Sami Kiminki
2009-06-18 16:00 ` Luis Useche [this message]
2009-06-19 6:46 ` Laurent Desnogues
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=20090618160030.GA7744@meg.local \
--to=luis@cs.fiu.edu \
--cc=qemu-devel@nongnu.org \
--cc=sami.kiminki@tkk.fi \
/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).