On 8 October 2018 at 23:17, Stefano Stabellini wrote:
> I double-checked all the addresses and they are correct. For some reason
> after starting the guest, ATS12NSOPW starts to fail for
> ffc006f91628, which is the same virtual address corresponding to the
> same runstate region allocated in
Hi Peter,
I am chasing an address translation error, and it looks like it might be
a QEMU bug, because I cannot reproduce the problem on a physical board.
The issue is that a requested ATS12NSOPW translation in Xen is reported
as failing by QEMU, but actually the address is correct. The workflow
