From: lmingcsce <Ming.Aaron.Liu@gmail.com>
To: xen-devel@lists.xensource.com
Subject: DomU memory update procedures ?
Date: Fri, 6 Jan 2012 08:41:55 -0800 (PST) [thread overview]
Message-ID: <1325868115079-5126037.post@n5.nabble.com> (raw)
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?
In my current understanding, I find that there is a hypercal do_mmu_update
in the hypervisor changing the content in the memory. 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.
next reply other threads:[~2012-01-06 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 16:41 lmingcsce [this message]
2012-01-09 9:57 ` DomU memory update procedures ? Tim Deegan
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=1325868115079-5126037.post@n5.nabble.com \
--to=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).