From: Julien Grall <julien@xen.org>
To: Andrei Cherechesu <andrei.cherechesu@nxp.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [Xen-devel] Having a DOM-U guest with 1:1 mapping in the second stage MMU.
Date: Thu, 13 Feb 2020 22:23:58 +0100 [thread overview]
Message-ID: <e5db3141-3557-f074-7fa3-e39ea6d8cf75@xen.org> (raw)
In-Reply-To: <VI1PR04MB5807A9BC95A9D956D052DB7DF91A0@VI1PR04MB5807.eurprd04.prod.outlook.com>
Hi,
On 13/02/2020 18:27, Andrei Cherechesu wrote:
> -----Original Message-----
> From: Julien Grall <julien@xen.org>
> Sent: Thursday, February 13, 2020 00:03
> To: Stefano Stabellini <sstabellini@kernel.org>; Andrei Cherechesu <andrei.cherechesu@nxp.com>
> Cc: Jorge Pereira <jorge.pereira@nxp.com>; xen-devel@lists.xenproject.org
> Subject: Re: [Xen-devel] Having a DOM-U guest with 1:1 mapping in the second stage MMU.
>
> Hello,
>
> I used the Xen from Stefano's tree and made the updates to the partial
> dtb that he specified.
>
>> This is mostly likely because Linux is trying to access a region
>> that is not mapped in stage-2. You can rebuild Xen with debug enabled
>> and you should see a message "traps.c:..." telling the exact physical
>> address accessed.
>>
>> In general I would recommend to build Xen with debug enabled during development as the hypervisor will give you more information of what's going on.
>>
>> Cheers,
>>
>> --
>> Julien Grall
>
> I enabled debug config and gave it another try. But I'm still
> getting the same unhandled fault error, that seems to match what
> Julien described above.
>
> It is indeed a stage-2 abort caused by the guest.
>
> I attached the DomU1 crash log at [0].
>
> [0] https://pastebin.com/BSHVFQiK
From the log:
(XEN) traps.c:1973:d1v0 HSR=0x939f0046 pc=0xffffff80083ac864
gva=0xffffff800800d048 gpa=0x000000402f0048
So the guest is trying to access the guest physical address
0x000000402f0048. Looking at the partial device tree you provided, you
are requesting Xen to map the range 0x4002f000 - 0x40030000.
The address does not belong to the range. Could you check whether you
did passthrough the correct range? (It seems like a zero is missing).
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-02-13 21:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 17:27 [Xen-devel] Having a DOM-U guest with 1:1 mapping in the second stage MMU Andrei Cherechesu
2020-02-13 21:23 ` Julien Grall [this message]
2020-02-13 21:28 ` Stefano Stabellini
2020-03-31 17:35 ` [EXT] " Andrei Cherechesu
2020-03-31 19:39 ` Stefano Stabellini
-- strict thread matches above, loose matches on Subject: below --
2020-04-01 19:58 Andrei Cherechesu
2020-04-01 21:07 ` Julien Grall
2020-04-01 21:35 ` Stefano Stabellini
2020-04-01 10:14 Andrei Cherechesu
2020-04-01 16:26 ` Stefano Stabellini
[not found] <VI1PR04MB5807A7F83F1B2763BD7EEB20F91B0@VI1PR04MB5807.eurprd04.prod.outlook.com>
2020-02-12 13:45 ` Andrei Cherechesu
2020-02-12 21:36 ` Stefano Stabellini
2020-02-12 22:03 ` Julien Grall
2020-01-14 21:39 Jorge Pereira
2020-01-15 11:07 ` Julien Grall
2020-01-16 23:55 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5db3141-3557-f074-7fa3-e39ea6d8cf75@xen.org \
--to=julien@xen.org \
--cc=andrei.cherechesu@nxp.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).