xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Peng Fan <van.freenix@gmail.com>, xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org
Subject: Re: SMMU, Unhandled context fault
Date: Tue, 26 Apr 2016 11:28:03 +0100	[thread overview]
Message-ID: <571F42B3.3090003@arm.com> (raw)
In-Reply-To: <20160425085406.GA28759@linux-7smt.suse>



On 25/04/2016 09:54, Peng Fan wrote:
> Hi Julien, Stefano

Hello Peng,

> I met an issue when passthrough a device to DomU, and have no clear idea what's wrong.

Which version of the SMMU is present on the board? Is it SMMUv1 or SMMUv2?

The SMMU drivers in Xen has been ported from Linux last year. It might 
be possible that some bug fixes need to be ported.

> "
> (XEN) smmu: /iommu@5c800000: Unhandled context fault: iova=0x42188000, fsynr=0x433, cb=0
> (XEN) smmu: /iommu@5c800000: Unhandled context fault: iova=0x42188020, fsynr=0x433, cb=0
> "

The IOVA corresponds to a guest RAM address. It would be useful if you 
provide the Xen boot logs.

> fsynr is 0x433, PTWF is 1, which means
> "An external fault occurred while processing a translation table walk"
>
> My DomU cfg is:
> "
> kernel = "/root/xen/Image"
> device_tree = "/root/xen/sdhc.dtb"
> dtdev = [ "/usdhc@5a240000" ]
> iomem = [ "0x5a240,0x10@0x1a240"]
> irqs = [ 257 ]
> memory = "128"
> name = "domU-sdhc-test"
> vcpus = 1
> serial="pty"
> disk = [ 'phy:/dev/loop0,xvda,w' ]
> extra = "console=hvc0 root=/dev/xvda debug=/bin/sh"
> "
>
> I saw this patch: http://www.gossamer-threads.com/lists/xen/devel/428030
> "xen/arm: Force broadcast of TLB and instruction cache maintenance instructions"
> So I guess should we have a similar fix for SMMU TLB?

That is different.

Xen only supports SMMU for stage-2 page table, so the hypervisor is in 
charge of flushing the SMMU TLBs when the translation IPA -> PA is changed.

The patch "xen/arm: Force broadcast..." will set HCR_EL2.FB to upgrade 
any local flush instruction made by a guest into innershareable flush 
instruction.

>  From my failure log, It should be that TCU can not find the machine address for iova(guest physical address).

What do you mean by TCU?

Regards,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-04-26 10:28 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 [this message]
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
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=571F42B3.3090003@arm.com \
    --to=julien.grall@arm.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).