qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Basim Baig <basimbaig@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU Memory subsystem
Date: Fri, 21 Jun 2013 15:04:28 +0800	[thread overview]
Message-ID: <51C3FAFC.3020700@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAHPk7wS9hV7Em=NLBxQwYiJACa3GJwgkXLCR42a8F1LP4utHOA@mail.gmail.com>

于 2013-6-21 9:51, Basim Baig 写道:
> 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.
>
> Thanks,
> Mirza Basim Baig
> Stony Brook University
>
   I think you can archieve your goal relative easily in soft-mmu mode,
but in KVM case, you will need to dig a bit in kvm.ko in kernel source
code.

-- 
Best Regards

Wenchao Xia

  reply	other threads:[~2013-06-21  7:05 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 [this message]
2013-06-21 16:16 ` Lluís Vilanova
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=51C3FAFC.3020700@linux.vnet.ibm.com \
    --to=xiawenc@linux.vnet.ibm.com \
    --cc=basimbaig@gmail.com \
    --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).