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

[Xen-devel] [NEO 1:1] Nativedom 1:1 Mapping


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Guy Zana" <guy@xxxxxxxxxxxx>
  • Date: Fri, 21 Sep 2007 03:46:16 -0400
  • Delivery-date: Fri, 21 Sep 2007 00:48:03 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acf7nOHWOm+J+TgmQSWCP5gB/ehOoA==
  • Thread-topic: [NEO 1:1] Nativedom 1:1 Mapping

This patch applies to c/s #15522.
 
Nativedom 1:1 memory enabling - Done by "stealing" memory from Xen's
e820 at 
boot time. The pages are later being allocated to NativeDom using a
special
allocator.
 
    x86-64
    ======
    
    The 512KB-1MB region is remapped (because of the ROMs) to an address
    above 16MB.
 
    As far as NativeDom can see:
        1. The 0-512KB region is marked as USABLE
        2. The 512KB-1MB region is marked as RESERVED
 
    x86-32
    ======
    
    The 0-12MB region is remapped because it contains the ROMs and xen
itself.
    Drawback - If a guest allocates a DMA buffer in this region, there
is a
    chance that the machine would crash.
 
* Setup.c - Added boot parameters & NativeDom memory initialization
* Page_alloc.c - The 1:1 memory allocator was added

The patch may contain small vt-d code chunks, these got in because of
the merge, please disregard them for now.
 
Thanks,
Guy.

Attachment: nativedom-1to1.patch
Description: nativedom-1to1.patch

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

 


Rackspace

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