From mboxrd@z Thu Jan  1 00:00:00 1970
From: lmingcsce <Ming.Aaron.Liu@gmail.com>
Subject: DomU memory update procedures ?
Date: Fri, 6 Jan 2012 08:41:55 -0800 (PST)
Message-ID: <1325868115079-5126037.post@n5.nabble.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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.