Re: [PATCH V3] xen: eliminate scalability issues from initial mapping setup

From: Juergen Gross
Date: Fri Sep 26 2014 - 03:54:23 EST

On 09/24/2014 03:20 PM, David Vrabel wrote:
On 17/09/14 15:59, 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.

This doesn't seem to work. It crashes when attempting to construct
the page tables. Have these patches been tested on a host with > 512 GiB?

After some tests on a machine with 1 TB memory I think this patch makes
sense only if the booted domain will be capable of using all the memory.
Ignoring everything above 512 GB will not work as the hypervisor is
putting vital information in this region (mfn_list, initrd, ...).

So please ignore this patch. I'm trying to setup a solution using a
virtually mapped linear p2m list.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at