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

Re: [Xen-devel] XEN on R-CAR H3

Hi Oleksandr,

On 20/02/2019 21:28, Oleksandr Tyshchenko wrote:
> ср, 20 февр. 2019 г., 22:14 Julien Grall <julien.grall@xxxxxxx 
> <mailto:julien.grall@xxxxxxx>>:
> If I am not mistaken, the diff between BSP's and mainline device trees is in 
> reserved memory area. BSP device tree (1) contains reserved memory regions, 
> but 
> the mainline one (2) doesn't.
>  From the log you provided, I see that Xen is trying to copy device-tree to 
> the 
> address which is located in reserved area (0x58000000). FYI, we always remove 
> these reserved area nodes from the device-tree. Maybe that's why we didn't 
> face 
> an issue. Julien, what do you think, can this be a reason?
While I know that Xen does not deal with reserved area yet, we should have been 
able to write in that region. We don't even reach that state as we can't get 
associated page.

It might be possible that the p2m entry is overwritten when going through the 
for mapping all the regions (see handle_device).

Printing the lookup would actually help to know what's going on.


Julien Grall
Xen-devel mailing list



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