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-ppc-devel

[XenPPC] JS21 and Dom0 memory

In case you missed it, Dom0 will get more memory now beyond the RMA.
The default is 1/16th of memory or 192M which ever is larger.

The 1/16th is suggested by the x86 Xen build
The 192M comes from noting that > 128M is good and <= 256 is enuff to make my maple (512M max) happy, so 256M - 64M. Performance is now way better and the JS21 should have access to their disks as rootfs.

You can change this amount my adding "dom0_mem=<n>[Gg|Mm|Kk|Bb]" to your Xen options.
-JX


# HG changeset patch
# User Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
# Node ID f8233165fb80982c36cc8a124c6e017821805843
# Parent  228d1441ee7207d56400aa455e57ca68ad6c5729
[POWERPC][XEN] Allocate more memory than RMA for Dom0

The following patch will only effect Dom0 at the moment and allow it
to be created with memory larger than RMA.  It works by allocating
extents (AKA chunks) of memory of an order specified by the processor.
The extent size should be a value that is capabable of mapping a
"large page" so we use the 970s large page size.  These extents are
tracked by an extents list that simply tracks these page allocations
and what there mapping is.  Other sub-systems effected by this:
  - Dom0 OFD devtree /memory cleanup
  - log_large_page_sizes is now an array
  - Config for minumum Dom0 size

Caveats:
 - There is a hack around HTAB allocation because we currently
   allocate one at domain creation time, this will be correct by a
   patch to follow.
 - Dom0, or domains capable of mapping mfns byt have their extents be
   PFN=MFN


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