From: Tim Deegan <tim@xen.org>
To: lmingcsce <Ming.Aaron.Liu@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: DomU memory update procedures ?
Date: Mon, 9 Jan 2012 09:57:44 +0000 [thread overview]
Message-ID: <20120109095744.GC26595@ocelot.phlegethon.org> (raw)
In-Reply-To: <1325868115079-5126037.post@n5.nabble.com>
Hi,
At 08:41 -0800 on 06 Jan (1325839315), lmingcsce wrote:
> Hi, I have a question about memory update of DomU.
> When DomU writes a new value to a memory address, how does hypervisor change
> the value in the particular address and change the dirty page bit?
The hypervisor is not usually involved in writing the contents of the
memory -- that's just done my the CPU in the normal way. The same is
true for the dirty bit in the PTE.
In some cases the hypervisor has to emulate an instruction. The code
for the emulator is in x86_emulate.c; the pagetable walker is in
arch/x86/mm/guest_walk.c.
> In my current understanding, I find that there is a hypercal do_mmu_update
> in the hypervisor changing the content in the memory.
do_mmu_update() is used by PV domU to change its pagetables; it's not
involved in normal memory writes.
Cheers,
Tim.
> However, I want to
> know the details about the memory update procedures. Or you can simply tell
> me how can I find this procedures.
> Thanks for your help.
>
> --
> View this message in context: http://xen.1045712.n5.nabble.com/DomU-memory-update-procedures-tp5126037p5126037.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2012-01-09 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 16:41 DomU memory update procedures ? lmingcsce
2012-01-09 9:57 ` Tim Deegan [this message]
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=20120109095744.GC26595@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Ming.Aaron.Liu@gmail.com \
--cc=xen-devel@lists.xensource.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).