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

[Xen-devel] Shadow pagetable code

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Shadow pagetable code
From: Yongjun Jeon <yongjunj@xxxxxxxxxxx>
Date: Thu, 12 Jul 2007 16:10:50 -0400 (EDT)
Delivery-date: Tue, 17 Jul 2007 05:07:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

There's been a significant design change in the shadow pagetable code in Xen 3.1.0 compared to last year's 3.0.2 release. I don't know if people have seen my last post, but here's what I'd like to know:

1. Is everyone aware of this design change?

2. Has this design change been documented, i.e. is there any source that documents how the old functions map to the new design?

I'm basically trying to forward-port the Potemkin patch released for Xen 3.0.2, which implements delta virtualization (copy-on-write optimization for flash cloning domains) using the Xen translated shadow memory model.

Any input would be much appreciated.

Thanks,
Jun


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

<Prev in Thread] Current Thread [Next in Thread>