On 23/09/14 04:58, Juergen Gross wrote: > On 09/17/2014 04:59 PM, Juergen Gross wrote: >> Direct Xen to place the initial P->M table outside of the initial >> mapping, as otherwise the 1G (implementation) / 2G (theoretical) >> restriction on the size of the initial mapping limits the amount >> of memory a domain can be handed initially. >> >> As the initial P->M table is copied rather early during boot to >> domain private memory and it's initial virtual mapping is dropped, >> the easiest way to avoid virtual address conflicts with other >> addresses in the kernel is to use a user address area for the >> virtual address of the initial P->M table. This allows us to just >> throw away the page tables of the initial mapping after the copy >> without having to care about address invalidation. >> >> It should be noted that this patch won't enable a pv-domain to USE >> more than 512 GB of RAM. It just enables it to be started with a >> P->M table covering more memory. This is especially important for >> being able to boot a Dom0 on a system with more than 512 GB memory. >> >> Signed-off-by: Juergen Gross <jgr...@suse.com> >> Signed-off-by: Jan Beulich <jbeul...@suse.com> > > Any Acks/Naks?
Sorry for the delay. We only have one machine with 1 TB of RAM and it's very busy. >> +static void xen_cleanmfnmap_free_pgtbl(void *pgtbl) This needs to be __init. But I'll fix this up. In future, can you make sure you build with the option that finds these (CONFIG_DEBUG_SECTION_MISMATCH). David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
