[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen at scale
> It needs to be something other than page tables, really. I'm inclined > to pass the new domain a preinitialised 'phys->machine' translation > table, and only create initial page tables large enough to contain the > kernel image, initial page tables, and the translation table. 16MB of > VA space would be plenty. VA should probably have the size of text+data+bss. My preferred layout would be pagetables/pgd/p2m-mapping at the end of the domain's physical memory in that order. And this should then be either mapped at VA 0, end aligned with text or end aligned with the hypervisor memory. I think I'd choose end aligned with the hypervisor memory. > As for breaking the interface to other types of guest OS > (ie. non-Linux) -- they can implement their own domain builder that > sets memory out just as they like. How's that supposed to work for non-Linux domain0 guests? christian ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |