From: "Lluís Vilanova" <vilanova@ac.upc.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU Memory subsystem
Date: Fri, 21 Jun 2013 18:16:48 +0200 [thread overview]
Message-ID: <871u7v1lsf.fsf@fimbulvetr.bsc.es> (raw)
In-Reply-To: <CAHPk7wS9hV7Em=NLBxQwYiJACa3GJwgkXLCR42a8F1LP4utHOA@mail.gmail.com> (Basim Baig's message of "Thu, 20 Jun 2013 21:51:51 -0400")
Basim Baig writes:
> Hello,
> I am currently working on a project where I aim to log every memory access made
> by a virtual machine running inside of QEMU (for analyzing kernel behavior). My
> initial approach is to possibly hook into the QEMU mmu implementation and find
> the place where the guest->host page translation or lookup is done. In this way
> I can know any pages accessed by the guest (This is only the first level.
> Eventually I would want to get logging at pointer granularity). I have been
> reading through the source code and online documentations for a week now to get
> a general sense of the qemu internals and codebase.
> I just wanted some advice on what direction I should head to (or who I can talk
> to) If I really want to get into depth of how I can make significant changes to
> qemu memory management and mmu subsystem.
This might provide what you're asking (event 'vmem'):
https://projects.gso.ac.upc.edu/projects/qemu-dbi/wiki
Lluis
--
"And it's much the same thing with knowledge, for whenever you learn
something new, the whole world becomes that much richer."
-- The Princess of Pure Reason, as told by Norton Juster in The Phantom
Tollbooth
next prev parent reply other threads:[~2013-06-21 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 1:51 [Qemu-devel] QEMU Memory subsystem Basim Baig
2013-06-21 7:04 ` Wenchao Xia
2013-06-21 16:16 ` Lluís Vilanova [this message]
2013-06-22 20:43 ` Basim Baig
2013-07-17 15:19 ` Yaohui
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=871u7v1lsf.fsf@fimbulvetr.bsc.es \
--to=vilanova@ac.upc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.