From: Julien Grall <julien.grall@arm.com>
To: Peng Fan <van.freenix@gmail.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: xen-devel@lists.xenproject.org, sstabellini@kernel.org
Subject: Re: SMMU, Unhandled context fault
Date: Wed, 27 Apr 2016 10:58:28 +0100 [thread overview]
Message-ID: <57208D44.5080404@arm.com> (raw)
In-Reply-To: <20160427015315.GA26486@linux-7smt.suse>
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).
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-27 9:58 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 [this message]
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
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=57208D44.5080404@arm.com \
--to=julien.grall@arm.com \
--cc=edgar.iglesias@gmail.com \
--cc=sstabellini@kernel.org \
--cc=van.freenix@gmail.com \
--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).