From: Peng Fan <van.freenix@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
sstabellini@kernel.org, xen-devel@lists.xenproject.org
Subject: Re: SMMU, Unhandled context fault
Date: Fri, 29 Apr 2016 22:28:51 +0800 [thread overview]
Message-ID: <20160429142814.GA11154@linux-7smt.suse> (raw)
In-Reply-To: <57220CD2.9060905@arm.com>
Hi Julien,
On Thu, Apr 28, 2016 at 02:14:58PM +0100, Julien Grall wrote:
>Hello,
>
>On 28/04/16 13:56, Peng Fan wrote:
>>On Thu, Apr 28, 2016 at 11:27:22AM +0100, Julien Grall wrote:
>>>
>>>
>>>On 28/04/16 07:39, Peng Fan wrote:
>>>>Hi Julien,
>>>
>>>Hello Peng,
>>>
>>>>On Thu, Apr 28, 2016 at 10:37:54AM +0800, Peng Fan wrote:
>>>>>Hi Julien,
>>>>>On Wed, Apr 27, 2016 at 10:58:28AM +0100, Julien Grall wrote:
>>>>>>Hello Peng,
>>>>>>
>>>>>>On 27/04/2016 03:02, Peng Fan wrote:
>>>>>>>On Tue, Apr 26, 2016 at 04:30:03PM +0200, Edgar E. Iglesias wrote:
>>>>>>>>On Tue, Apr 26, 2016 at 09:56:33PM +0800, Peng Fan wrote:
>>>>>>>>>You mean the PNU bit(Privileged Not Unprivileged) is 1?
>>>>>>>>>I did not met Unhandled context fault each time.
>>>>>>>>>Actually during my serveral boot test, I only met two times.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>I meant the NSSTATE and NSATTR bits in FSYNR are set to zero. I get the
>>>>>>>>impression that the TrustZone state for the SD controller may be
>>>>>>>
>>>>>>>oh. The NSATTR bit is 0. I did not find NSSTATE in my Issue D SMMU spec.
>>>>>>>If without xen, only one linux boots up, sd controller can access memory using
>>>>>>>DMA without issue.
>>>>>>
>>>>>>IIRC, by default Linux baremetal does not protect the devices with the SMMU.
>>>>>>
>>>>>>I would recommend you to check whether the SMMUs are in-used and configured
>>>>>>to generate a fault (disable_bypass = 1).
>>>>>
>>>>>Ok. I'll set S2CRn to generate fault in xen smmu driver to see whether SMMUs in-used or not
>>>
>>>I meant in Linux.
>>
>>My bad. Do you mean enabling SMMU driver in Linux with KVM support?
>
>Yes.
>
>[...]
>
>>Is there any big difference between XEN SMMU driver and linux SMMU driver?
>>I know that XEN only support Stage 2. But the initliaization flow is almost the same.
>
>The SMMU driver for Xen is a port from Linux 3.19-rc0. Since then the Linux
>driver has been reworked and it might be possible that we have missed some
>bug fix.
>
>Aside that, for Xen, the page tables are always shared between the SMMU and
>the processor.
Thanks. I shared two picture that dumped using TRACE32.
https://drive.google.com/file/d/0B9ruJqJLIGp7cHhhSFNSNC00MHc/view?usp=sharing
https://drive.google.com/file/d/0B9ruJqJLIGp7dmlqVllXYTIxajQ/view?usp=sharing
Would you please help check?
The block that marked red, seems not correct. I am also adding debug info
in xen memory allocation part to see what happends.
Thanks,
Peng.
>
>Regards,
>
>--
>Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-29 14:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 8:54 SMMU, Unhandled context fault Peng Fan
2016-04-26 10:28 ` Julien Grall
2016-04-26 11:50 ` Peng Fan
2016-04-26 13:12 ` Edgar E. Iglesias
2016-04-26 13:56 ` Peng Fan
2016-04-26 14:30 ` Edgar E. Iglesias
2016-04-27 2:02 ` Peng Fan
2016-04-27 9:58 ` Julien Grall
2016-04-28 2:37 ` Peng Fan
2016-04-28 6:39 ` Peng Fan
2016-04-28 10:27 ` Julien Grall
2016-04-28 12:56 ` Peng Fan
2016-04-28 13:14 ` Julien Grall
2016-04-29 14:28 ` Peng Fan [this message]
2016-05-03 10:58 ` Julien Grall
2016-05-03 13:58 ` Peng Fan
2016-05-06 12:48 ` Julien Grall
2016-05-08 11:52 ` Peng Fan
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=20160429142814.GA11154@linux-7smt.suse \
--to=van.freenix@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=julien.grall@arm.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).