ia64/xen-unstable

changeset 2781:10ffc8273164

bitkeeper revision 1.1159.1.310 (41828879uBRmYC81TaPfV6LGMJ1TYw)

Doc fixes.
author kaf24@freefall.cl.cam.ac.uk
date Fri Oct 29 18:14:17 2004 +0000 (2004-10-29)
parents 9b7a35c0e304
children c48afdf6aa0f
files README TODO
line diff
     1.1 --- a/README	Fri Oct 29 17:57:57 2004 +0000
     1.2 +++ b/README	Fri Oct 29 18:14:17 2004 +0000
     1.3 @@ -8,7 +8,7 @@
     1.4  ###############################
     1.5  
     1.6  University of Cambridge Computer Laboratory
     1.7 -28 October 2004
     1.8 +29 October 2004
     1.9  
    1.10  http://www.cl.cam.ac.uk/netos/xen/
    1.11  http://www.cl.cam.ac.uk/netos/xen/
    1.12 @@ -16,17 +16,18 @@ http://www.cl.cam.ac.uk/netos/xen/
    1.13  About the Xen Virtual Machine Monitor
    1.14  =====================================
    1.15  
    1.16 -"Xen" is a Virtual Machine Monitor (VMM) originally developed by the
    1.17 +Xen is a Virtual Machine Monitor (VMM) originally developed by the
    1.18  Systems Research Group of the University of Cambridge Computer
    1.19 -Laboratory, as part of the UK-EPSRC funded XenoServers project. 
    1.20 +Laboratory, as part of the UK-EPSRC funded XenoServers project.
    1.21  
    1.22 -Xen 2.0 offers excellent performance, hardware support and enterprise
    1.23 -grade features such as live migration.  Linux 2.6, 2.4 and NetBSD 2.0
    1.24 -are already available for Xen, with more operating system ports on the
    1.25 -way.
    1.26 +The 2.0 release offers excellent performance, hardware support and
    1.27 +enterprise-grade features such as live migration. Linux 2.6, 2.4 and
    1.28 +NetBSD 2.0 are already available for Xen, with more operating system
    1.29 +ports on the way.
    1.30  
    1.31 -Xen is Free Open Source Software, released under the GNU GPL.
    1.32 +Xen is freely-distributable Open Source software, released under the
    1.33 +GNU GPL.
    1.34  
    1.35 -For full documentation, see the Xen User Manual in docs/user.pdf
    1.36 +For full documentation, see the Xen User Manual in docs/pdf/user.pdf
    1.37  (after running make -C docs) or the Documentation page on the Xen
    1.38  website.
     2.1 --- a/TODO	Fri Oct 29 17:57:57 2004 +0000
     2.2 +++ b/TODO	Fri Oct 29 18:14:17 2004 +0000
     2.3 @@ -12,7 +12,7 @@ make this release: We have plans for a "
     2.4  enables otherwise unused system memory to be used by domains in a
     2.5  read-only fashion.
     2.6  
     2.7 -Disk Scheduling
     2.8 +Disk scheduling
     2.9  ---------------
    2.10  The current disk scheduler is rather simplistic (batch round robin),
    2.11  and could be replaced by e.g. Cello if we have QoS isolation
    2.12 @@ -27,7 +27,7 @@ assigned to a CPU when they are created 
    2.13  We'd like to see a user-space load-balancing daemon that can shift
    2.14  domains between CPUs as their activity changes.
    2.15  
    2.16 -Multiprocessor Guest VMs
    2.17 +Multiprocessor guest VMs
    2.18  ------------------------
    2.19  Xen currently only supports uniprocessor guest OSes. We have designed
    2.20  the Xen interface with MP guests in mind, and plan to build an MP
    2.21 @@ -40,7 +40,7 @@ still has the page in its TLB to ensure 
    2.22  other issue for supporting MP guests is that we'll need some sort of
    2.23  CPU gang scheduler, which will require some research.
    2.24  
    2.25 -Cluster Management
    2.26 +Cluster management
    2.27  ------------------
    2.28  There have been discussions regarding a unified cluster controller
    2.29  for Xen deployments.  This would leverage the existing features of
    2.30 @@ -48,12 +48,13 @@ Xen to present a uniform control interfa
    2.31  as a pool of resources, rather than a set of completely distinct
    2.32  machines.
    2.33  
    2.34 -PAE Support on 32-bit x86
    2.35 --------------------------
    2.36 -Xen can currently use up to 4GB of memory. It's possible for x86
    2.37 -machines to address more than that (64GB), but it requires using a
    2.38 -different page table format (3-level rather than 2-level) that we
    2.39 -currently don't support. Adding 3-level PAE support wouldn't be
    2.40 -difficult, but we'd also need to add support to all the guest
    2.41 -OSs. We do not plan to add this support ourselves but volunteers
    2.42 -are welcome!
    2.43 +64-bit x86
    2.44 +----------
    2.45 +Xen can currently use up to 4GB of memory. It's possible for 32-bit
    2.46 +x86 machines to address up to 64GB, but it requires using a different
    2.47 +page table format that would be rather tedious to support. Our
    2.48 +preferred approach is to virtualize 64-bit x86 (x86/64), as supported
    2.49 +by modern AMD and Intel processors. The large address space provided
    2.50 +by a 64-bit execution model greatly simplifies support for large-memory
    2.51 +configurations. Our implementation for x86/64 is in progress and should
    2.52 +feature in our next major release.