Re: [PATCH] x86: use 'dom0_mem' to limit the number of pages for dom0

[David Vrabel <david.vrabel@citrix.com>]

On 16/08/11 13:51, Ian Campbell wrote:
> 
> The key difference is that classic-Xen kernels called both
> XENMEM_memory_map and XENMEM_machine_memory_map and dealt with both,
> whereas pvops (dom0) calls XENMEM_machine_memory_map and tries to figure
> out how much of the E820_RAM therein it can actually use based on
> nr_pages and such. You've used XENMEM_maximum_reservation in your
> followup series which I think is a suitable surrogate for calling
> XENMEM_memory_map (although I didn't check).

XENMEM_memory_map for dom0 doesn't work as nothing populates the map.

Classic-Xen kernels appear to invent a memory map based only on nr_pages
and it's non-obvious where it gets any other limit from (I didn't look
that hard though).

I did originally make XENMEM_memory_map work for dom0 but using
XENMEM_maximum_reservation looked more relevant.

David