[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] xen/arm64: do not (incorrectly) limit size of xenheap



On Fri, Sep 04, 2015 at 01:57:00PM +0100, Julien Grall wrote:
> The commit 88e3ed61642bb393458acc7a9bd2f96edc337190 "x86/NUMA: make
> init_node_heap() respect Xen heap limit" breaks boot on the arm64 board
> X-Gene.
> 
> The xenheap bits variable is used to know the last RAM MFN always mapped
> in Xen virtual memory. If the value is 0, it means that all the memory is
> always mapped in Xen virtual memory.
> 
> On X-gene the RAM bank resides above 128GB and last xenheap MFN is
> 0x4400000. With the new way to calculate the number of bits, xenheap_bits
> will be equal to 38 bits. This will result to hide all the RAM and the
> impossibility to allocate xenheap memory.
> 
> Given that aarch64 have always all the memory mapped in Xen virtual
> memory, it's not necessary to call xenheap_max_mfn which set the number
> of bits.
> 
> Suggested-by: Jan Beulich <jbeulich@xxxxxxxx>
> Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx>
> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
> 

Release-acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.