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] [RFC] XI Shadow Page Table Mechanism

To: Ben Thomas <bthomas@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC] XI Shadow Page Table Mechanism
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Wed, 21 Jun 2006 15:31:59 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 21 Jun 2006 13:32:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <44998B2C.2000109@xxxxxxxxxxxxxxx>
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>
References: <44998B2C.2000109@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.4 (X11/20060615)
Ben Thomas wrote:
This post contains the design document for what is currently known
as the "XI Shadow Mechanism".  This is a design for shadow
page table code for fully virtualized HVM domains running on a 64-bit
Xen hypervisor.

This work was undertaken to address a number of goals.  These are
enumerated in the document and include:

- ability to run fully virtualized 32, 32PAE and 64 bit guest
  domains concurrently on a 64-bit hypervisor
This isn't supported currently?  Since an HVM must go through 16 bit, 32 
bit, and 64 bit mode to boot up, how can we start more than one guest at 
a time currently if this doesn't already work?
- support live migration of fully virtualized domains
Sweet.  What about the current shadow page code limited this?

- provide good performance and robustness

This design has been implemented and is currently being tested.
It has been supporting the variety of memory models as noted above,
and using widely used Windows and Linux distributions (SuSe,
RedHat and others). At a point in the near future, a patch
will be available.

This design center is the x86-64 architecture. It is not our
intent to completely replace all shadow page management, and
we've attempted to limit the scope of change.

A preliminary version of this design concept has undergone
brief review with some members of the Xen community. We hope
that this is of value to the Xen community and welcome your
feedback and comments.
Can't really comment as it's not quotable.  Some questions that 
immediately come to mind are:
- how do you deal with large pages within the hypervisor?  do you 
coalesce or just hope there is contiguous pages available?
- what is the performance benefit in saving the shadow pages for each 
domain?  there's clearly a memory trade-off here so understanding the 
performance gain seems important.
- OOM can be dealt with in the existing code by just invalidating 
existing mappings to free up pages.  what advantages do your approach 
have to this?  (i realize we don't do this today but in theory, we could).
Interesting stuff.  I'm eager to see the code.

Regards,

Anthony Liguori

Thanks,
-b

------------------------------------------------------------------------

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

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

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