From: Wei Chen <Wei.Chen@arm.com>
To: xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, wei.chen@arm.com, steve.capper@arm.com,
Kaly.Xin@arm.com, julien.grall@arm.com, nd@arm.com
Subject: [PATCH 3/7] xen/arm: Prepare SMMU resources for protected devices
Date: Fri, 30 Jun 2017 11:15:07 +0800 [thread overview]
Message-ID: <1498792511-25149-4-git-send-email-Wei.Chen@arm.com> (raw)
In-Reply-To: <1498792511-25149-1-git-send-email-Wei.Chen@arm.com>
In previous code, while we are constructing Dom0, we will assign
all devices except passthrough devices to Dom0. In the later, when
we start the DomU, the assign_device will prepare SMMU resources
for the devices passthrough to DomU. This is ok when we kept the
add_device code in assign_device. But currently, we have separated
add_device from assign_device. If we don't prepare SMMU resources
for passthrough devices, these devices would not work properly in
DomU.
So, while we are handling all devices DT node in construction Dom0,
we will call add_device to prepare SMMU resources for all protected
devices, regardless of passthrough or not.
Signed-off-by: Wei Chen <Wei.Chen@arm.com>
---
xen/arch/arm/domain_build.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index c6776d7..6aea427 100644
--- a/xen/arch/arm/domain_build.c
+++ b/xen/arch/arm/domain_build.c
@@ -1082,6 +1082,18 @@ static int handle_device(struct domain *d, struct dt_device_node *dev,
dt_dprintk("%s passthrough = %d nirq = %d naddr = %u\n",
dt_node_full_name(dev), need_mapping, nirq, naddr);
+ /*
+ * If this device is behind the SMMU, the add_device callback will
+ * prepare resource for it. Otherwise, add_device has no effect.
+ */
+ res = iommu_add_dt_device(d, dev);
+ if ( res )
+ {
+ printk(XENLOG_ERR "Failed to add device to IOMMU for %s\n",
+ dt_node_full_name(dev));
+ return res;
+ }
+
if ( dt_device_is_protected(dev) && need_mapping )
{
dt_dprintk("%s setup iommu\n", dt_node_full_name(dev));
--
2.7.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-30 3:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 3:15 [PATCH 0/7] Generic IOMMU bindings support for Xen platform devices Wei Chen
2017-06-30 3:15 ` [PATCH 1/7] xen/arm: SMMU: Implement the add_device callback in SMMU Wei Chen
2017-07-03 21:58 ` Stefano Stabellini
2017-07-04 5:37 ` Wei Chen
2017-07-05 17:57 ` Stefano Stabellini
2017-07-06 2:16 ` Wei Chen
2017-07-04 15:40 ` Julien Grall
2017-07-05 7:06 ` Wei Chen
2017-06-30 3:15 ` [PATCH 2/7] xen/arm: SMMU: Introduce a helper to add DT device to SMMU Wei Chen
2017-07-03 22:02 ` Stefano Stabellini
2017-07-04 5:45 ` Wei Chen
2017-07-05 18:02 ` Stefano Stabellini
2017-07-06 2:20 ` Wei Chen
2017-06-30 3:15 ` Wei Chen [this message]
2017-07-03 22:05 ` [PATCH 3/7] xen/arm: Prepare SMMU resources for protected devices Stefano Stabellini
2017-06-30 3:15 ` [PATCH 4/7] xen/arm: SMMU: Detect types of device tree binding Wei Chen
2017-07-03 22:30 ` Stefano Stabellini
2017-07-04 6:20 ` Wei Chen
2017-07-05 18:08 ` Stefano Stabellini
2017-07-06 2:25 ` Wei Chen
2017-06-30 3:15 ` [PATCH 5/7] xen/arm: SMMU: Keep registering legacy master in SMMU probe Wei Chen
2017-07-03 22:32 ` Stefano Stabellini
2017-06-30 3:15 ` [PATCH 6/7] xen/arm: SMMU: Support generic IOMMU bindings Wei Chen
2017-07-03 22:59 ` Stefano Stabellini
2017-07-04 6:27 ` Wei Chen
2017-07-04 7:26 ` Julien Grall
2017-07-05 7:04 ` Wei Chen
2017-07-05 13:07 ` Julien Grall
2017-07-06 2:11 ` Wei Chen
2017-07-05 18:15 ` Stefano Stabellini
2017-07-06 2:45 ` Wei Chen
2017-06-30 3:15 ` [PATCH 7/7] xen: Fix a typo in error message of iommu_do_dt_domctl Wei Chen
2017-07-03 21:53 ` 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=1498792511-25149-4-git-send-email-Wei.Chen@arm.com \
--to=wei.chen@arm.com \
--cc=Kaly.Xin@arm.com \
--cc=julien.grall@arm.com \
--cc=nd@arm.com \
--cc=sstabellini@kernel.org \
--cc=steve.capper@arm.com \
--cc=xen-devel@lists.xen.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).