linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/16] iommu: Introduce iommu domain types
Date: Thu, 26 Mar 2015 13:43:05 +0100	[thread overview]
Message-ID: <1427373799-18662-3-git-send-email-joro@8bytes.org> (raw)
In-Reply-To: <1427373799-18662-1-git-send-email-joro@8bytes.org>

From: Joerg Roedel <jroedel@suse.de>

This allows to handle domains differently based on their
type in the future. An IOMMU driver can implement certain
optimizations for DMA-API domains for example.

The domain types can be extended later and some of the
existing domain attributes can be migrated to become domain
flags.

Signed-off-by: Joerg Roedel <jroedel@suse.de>
---
 drivers/iommu/iommu.c |  5 +++--
 include/linux/iommu.h | 27 ++++++++++++++++++++++++++-
 2 files changed, 29 insertions(+), 3 deletions(-)

diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
index 11de262..4920605 100644
--- a/drivers/iommu/iommu.c
+++ b/drivers/iommu/iommu.c
@@ -909,14 +909,15 @@ struct iommu_domain *iommu_domain_alloc(struct bus_type *bus)
 	ops = bus->iommu_ops;
 
 	if (ops->domain_alloc)
-		domain = ops->domain_alloc();
+		domain = ops->domain_alloc(IOMMU_DOMAIN_UNMANAGED);
 	else
 		domain = kzalloc(sizeof(*domain), GFP_KERNEL);
 
 	if (!domain)
 		return NULL;
 
-	domain->ops = bus->iommu_ops;
+	domain->ops  = bus->iommu_ops;
+	domain->type = IOMMU_DOMAIN_UNMANAGED;
 
 	if (ops->domain_init && domain->ops->domain_init(domain))
 		goto out_free;
diff --git a/include/linux/iommu.h b/include/linux/iommu.h
index 69d1d12..72d03fe 100644
--- a/include/linux/iommu.h
+++ b/include/linux/iommu.h
@@ -51,7 +51,32 @@ struct iommu_domain_geometry {
 	bool force_aperture;       /* DMA only allowed in mappable range? */
 };
 
+/* Domain feature flags */
+#define __IOMMU_DOMAIN_PAGING	(1U << 0)  /* Support for iommu_map/unmap */
+#define __IOMMU_DOMAIN_DMA_API	(1U << 1)  /* Domain for use in DMA-API
+					      implementation              */
+#define __IOMMU_DOMAIN_PT	(1U << 2)  /* Domain is identity mapped   */
+
+/*
+ * This are the possible domain-types
+ *
+ *	IOMMU_DOMAIN_BLOCKED	- All DMA is blocked, can be used to isolate
+ *				  devices
+ *	IOMMU_DOMAIN_IDENTITY	- DMA addresses are system physical addresses
+ *	IOMMU_DOMAIN_UNMANAGED	- DMA mappings managed by IOMMU-API user, used
+ *				  for VMs
+ *	IOMMU_DOMAIN_DMA	- Internally used for DMA-API implementations.
+ *				  This flag allows IOMMU drivers to implement
+ *				  certain optimizations for these domains
+ */
+#define IOMMU_DOMAIN_BLOCKED	(0U)
+#define IOMMU_DOMAIN_IDENTITY	(__IOMMU_DOMAIN_PT)
+#define IOMMU_DOMAIN_UNMANAGED	(__IOMMU_DOMAIN_PAGING)
+#define IOMMU_DOMAIN_DMA	(__IOMMU_DOMAIN_PAGING |	\
+				 __IOMMU_DOMAIN_DMA_API)
+
 struct iommu_domain {
+	unsigned type;
 	const struct iommu_ops *ops;
 	void *priv;
 	iommu_fault_handler_t handler;
@@ -117,7 +142,7 @@ struct iommu_ops {
 	void (*domain_destroy)(struct iommu_domain *domain);
 
 	/* Domain allocation and freeing by the iommu driver */
-	struct iommu_domain *(*domain_alloc)(void);
+	struct iommu_domain *(*domain_alloc)(unsigned iommu_domain_type);
 	void (*domain_free)(struct iommu_domain *);
 
 	int (*attach_dev)(struct iommu_domain *domain, struct device *dev);
-- 
1.9.1

  parent reply	other threads:[~2015-03-26 12:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 12:43 [PATCH 00/16 v2] iommu: Move domain allocation into drivers Joerg Roedel
2015-03-26 12:43 ` [PATCH 01/16] iommu: Introduce domain_alloc and domain_free iommu_ops Joerg Roedel
2015-03-26 12:43 ` Joerg Roedel [this message]
2015-03-26 12:52   ` [PATCH 02/16] iommu: Introduce iommu domain types Swapna Nannapaneni
2015-03-26 12:43 ` [PATCH 03/16] iommu: Only allow iommu_map/unmap for paging domains Joerg Roedel
2015-03-26 12:43 ` [PATCH 04/16] iommu/amd: Make use of domain_alloc and domain_free Joerg Roedel
2015-03-26 12:43 ` [PATCH 05/16] iommu/vt-d: " Joerg Roedel
2015-03-26 12:43 ` [PATCH 06/16] iommu/omap: " Joerg Roedel
2015-03-26 12:43 ` [PATCH 07/16] iommu/arm-smmu: " Joerg Roedel
2015-03-26 12:43 ` [PATCH 08/16] iommu/exynos: " Joerg Roedel
2015-03-26 12:43 ` [PATCH 09/16] iommu/tegra-smmu: " Joerg Roedel
2015-03-27 10:59   ` Thierry Reding
2015-03-26 12:43 ` [PATCH 10/16] iommu/tegra-gart: " Joerg Roedel
2015-03-27 11:00   ` Thierry Reding
2015-03-26 12:43 ` [PATCH 11/16] iommu/msm: " Joerg Roedel
2015-03-26 12:43 ` [PATCH 12/16] iommu/shmobile: " Joerg Roedel
2015-03-26 12:43 ` [PATCH 13/16] iommu/ipmmu-vmsa: " Joerg Roedel
2015-03-26 12:43 ` [PATCH 14/16] iommu/rockchip: " Joerg Roedel
2015-03-26 12:43 ` [PATCH 15/16] iommu/fsl: " Joerg Roedel
2015-04-12 14:25   ` Varun Sethi
2015-03-26 12:43 ` [PATCH 16/16] iommu: Remove domain_init and domain_free iommu_ops Joerg Roedel
2015-03-27 11:03 ` [PATCH 00/16 v2] iommu: Move domain allocation into drivers Thierry Reding
2015-03-27 16:39 ` Heiko Stuebner
2015-03-28  4:24 ` Alex Williamson
2015-03-31 13:14   ` Joerg Roedel
2015-03-30 17:43 ` Will Deacon
2015-03-31 13:18   ` Joerg Roedel
2015-03-31 13:33 ` Joerg Roedel

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=1427373799-18662-3-git-send-email-joro@8bytes.org \
    --to=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.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).