[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] About log dirty mode during migration

  • To: xen-devel@xxxxxxxxxxxxx
  • From: lmingcsce <lmingcsce@xxxxxxxxx>
  • Date: Wed, 18 Jul 2012 21:57:55 -0400
  • Delivery-date: Thu, 19 Jul 2012 01:58:33 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

Hi All,
I have several questions about  log dirty mode during live migration. 
For my understanding, each time after XEN_DOMCTL_SHADOW_OP_CLEAN or 
XEN_DOMCTL_SHADOW_OP_PEEK operation, all the pages are set as read only. The 
following memory accesses to the memory pages will cause page fault (permission 
conflict) then using page_mark_dirty function to set the dirty bitmap. 
However, after I read the codes, I can't find the code places for the above 
a. Where is the exact place for the domain to set all the memory pages as read 
only? From paging_log_dirty_op function, I can see that when the operation is 
XEN_DOMCTL_SHADOW_OP_CLEAN, it will call clear_page. But what is the function 
of this one? Why doesn't  it do for XEN_DOMCTL_SHADOW_OP_PEEK? 
b. Where is the exact place for the domain to trap into hypervisor because of 
permission conflict and then set the memory pages are RW? 
I really can't find the places in the code. Thanks for your help. 

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.