WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: Making pages writable again in paging_log_dirty mode

To: Mike Sun <msun@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Making pages writable again in paging_log_dirty mode
From: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Date: Mon, 5 Jan 2009 15:07:14 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 05 Jan 2009 07:07:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <e4e579070901050624q68115393ka97012b9147a2397@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <e4e579070812191308q77c3a398p6baa246cff5f7ab2@xxxxxxxxxxxxxx> <e4e579070812191359t1bd3a8cand9bb01cd62da9696@xxxxxxxxxxxxxx> <20090102100725.GB12729@xxxxxxxxxxxxxxxxxxxxx> <e4e579070901020850n1b897c1aob521bf28d125b420@xxxxxxxxxxxxxx> <20090102172058.GC12729@xxxxxxxxxxxxxxxxxxxxx> <e4e579070901031743v5234c2c7g4042f7795ba6c180@xxxxxxxxxxxxxx> <e4e579070901031955g266192d5ra7913c8cd2557fca@xxxxxxxxxxxxxx> <e4e579070901041509p13a25b4u9e980eb8c5472356@xxxxxxxxxxxxxx> <20090105101107.GD12729@xxxxxxxxxxxxxxxxxxxxx> <e4e579070901050624q68115393ka97012b9147a2397@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.17 (2007-11-01)
At 09:24 -0500 on 05 Jan (1231147482), Mike Sun wrote:
> Ah yes, I should probably explain what I'm doing.  I'm using the
> log-dirty mode to catch any writes to pages that I haven't yet
> "copied" via a background copy mechanism, similar to the live
> migration copy.  If I have copied it already, then I manually mark it
> dirty to indicate that it can be made writable again.  That's what I'm
> trying to do in this code.

Erm, did you know that if you mark the page as dirty the normal
page-fault path will fix up the shadow PTEs the next time they cause a
write fault?  Not as fast as fixing them all in bulk (a few thousand
cycles for each pagefault and VMEXIT) but should be functionally
correct.

Cheers,

Tim.

-- 
Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Citrix Systems (R&D) Ltd.
[Company #02300071, SL9 0DZ, UK.]

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel