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

Re: [Xen-devel] REGRESSION: Xen 4.13 RC5 fails to bootstrap Dom0 on ARM


On 17/12/2019 04:39, Roman Shaposhnik wrote:
On Mon, Dec 16, 2019 at 6:55 PM Stefano Stabellini
<sstabellini@xxxxxxxxxx> wrote:
On Mon, 16 Dec 2019, Roman Shaposhnik wrote:
If I sum all the memory sizes together I get 0x3ddfd000 which is 990M.
If so, I wonder how you could boot succesfully with dom0_mem=1024M even
on Xen 4.12... :-?

That is a very interesting observation indeed! I actually don't
remember where that device tree came from, but I think it was from one
of the Linaro sites.

This is mostly likely because of:

commit 6341a674573f1834f083f0ab0f5b36b075f9e02e
Author: Julien Grall <julien.grall@xxxxxxx>
Date:   Wed Aug 21 22:42:31 2019 +0100

xen/arm: domain_build: Don't continue if unable to allocate all dom0 banks

Xen will only print a warning if there are memory unallocated when using
    1:1 mapping (only used by dom0). This also includes the case where no
    memory has been allocated.

    It will bring to all sort of issues that can be hard to diagnostic for
    users (the warning can be difficult to spot or disregard).

If the users request 1GB of memory, then most likely they want the exact amount and not 512MB. So panic if all the memory has not been allocated.

    After this change, the behavior is the same as for non-1:1 memory
    allocation (used by domU).

    At the same time, reflow the message to have the format on a single

    Signed-off-by: Julien Grall <julien.grall@xxxxxxx>
    Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>


Julien Grall

Xen-devel mailing list



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