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/
Home Products Support Community News


[XenPPC] [RFC] 64mb Chunk Allocator

For Xen on PPC, each domain needs a section of real memory, starting at 'real address' 0x0, allowing code to run with translate off. The PPC LPAR facility allows a unique chunk of memory to be 'mapped' at real address 0x0 for each partition (via RMOR). Minimum size of a chunk is 64mb, and requires alignment. Today's Xen code sets-up a single 64mb chunk for each domain.

Proposal: (my interpretation of Jimi's ideas...)
        Simple 64mb chunk allocator, allowing multiple chunks per domain, and freeing chunks when a domain is destroyed

        - Find installed memory using 'ofd' structure. Currently memory discovery stops at 1st hole (whether I/O or sparse).
        - Use bit-vector to indicate available chunks; atomic updating for SMP
        - Linux 'sparse memory support' will allow holes between 64mb chunks within domain
Xen-ppc-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>