qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jinpeng Wei <weijp@cc.gatech.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] How to modify QEMU to capture memory operations of the guest OS?
Date: Mon, 27 Aug 2007 23:21:01 -0400 (EDT)	[thread overview]
Message-ID: <Pine.GSO.4.58.0708272319170.2425@gaia2.cc.gatech.edu> (raw)

Hi All,

I am wondering if it is possible to modify QEMU source code such that I
can log the memory operations by a guest OS. According to QEMU
documentation, it has a compiled code piece for each instruction of the
guest OS (or the simulated CPU?). Where is each instruction read and
replaced with the pre-compiled code? Is it in dyngen.c?  I read dyngen.c
but can not figure out how the replacement is done. Can anybody shed light
on this process as well as how the logging could be done?

Many thanks,
Jinpeng

-------------------------------
Jinpeng Wei
Ph.D. student
College of Computing
Georgia Institute of Technology
Atlanta, GA 30332-0280
http://www.cc.gatech.edu/~weijp

                 reply	other threads:[~2007-08-28  3:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.GSO.4.58.0708272319170.2425@gaia2.cc.gatech.edu \
    --to=weijp@cc.gatech.edu \
    --cc=qemu-devel@nongnu.org \
    /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).