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

Re: [Xen-devel] xen:arm boot failures after commit 1c92a2aa*



Hello Ian

On Wed, Sep 24, 2014 at 8:58 AM, Julien Grall <julien.grall@xxxxxxxxxx> wrote:
> Hi Ian,
>
> On 09/24/2014 03:16 PM, Ian Campbell wrote:
>> On Wed, 2014-09-24 at 05:36 -0700, Suriyan Ramasami wrote:
>> Thanks,
>>
>>> (XEN)   VTCR_EL2: 80003518
>>
>> THis has changed from 0x80003558 before this change (sorry, this was in
>> your original report too and I failed to spot it).
>>
>> The missing bit changes the starting level of the PT from L1 to L2,
>> which ain't gonna work very well ;-).
>>
>> I can't for the life of me figure out how/why this works on arndale, but
>> it does...
>
> It also works on Midway (without the patch below). I guess it depends on
> the position of the RAM in the p2m.
>
>> Anyway, does this fix it for you?
>>

This does indeed fix it for the OdroidXU.
(XEN) P2M: 40-bit IPA
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80003558

It now boots up fine!

Thanks
- Suriyan

>> 8<------------------
>>
>> From ada27d3a56ba89513721e24abe4a4bebee2ab9cf Mon Sep 17 00:00:00 2001
>> From: Ian Campbell <ian.campbell@xxxxxxxxxx>
>> Date: Wed, 24 Sep 2014 15:13:28 +0100
>> Subject: [PATCH] xen: arm: correct VTCR setting on arm32.
>>
>> 1c92a2aaf8c6 "xen: arm: support for up to 48-bit IPA addressing on
>> arm64" inadvertently changes the VTCR setting for 32-bit from
>> 0x80003558 to 0x80003518, changing the SL0 setting from 0x1 (p2m
>> starts at L1) to 0x0 (p2m starts at L2).
>>
>> For some (inexplicable) reason this doesn't cause any issue on
>> Arndale but it does on the OdroidXU.
>>
>> Reported-by: Suriyan Ramasami <suriyan.r@xxxxxxxxx>
>> Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
>
> Reviewed-by: Julien Grall <julien.grall@xxxxxxxxxx>
>
> Regards,
>
> --
> Julien Grall

_______________________________________________
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®.