[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [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 Implementation: - 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 Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-ppc-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |