From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/15] iommu: Introduce iommu domain types
Date: Tue, 27 Jan 2015 00:51:32 +0100 [thread overview]
Message-ID: <1422316305-19216-3-git-send-email-joro@8bytes.org> (raw)
In-Reply-To: <1422316305-19216-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.
Signed-off-by: Joerg Roedel <jroedel@suse.de>
---
drivers/iommu/iommu.c | 5 +++--
include/linux/iommu.h | 11 ++++++++++-
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
index 684efc0..ab24d77 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..0b67f65 100644
--- a/include/linux/iommu.h
+++ b/include/linux/iommu.h
@@ -51,7 +51,16 @@ struct iommu_domain_geometry {
bool force_aperture; /* DMA only allowed in mappable range? */
};
+/* This are the possible domain-types */
+enum iommu_domain_type {
+ IOMMU_DOMAIN_DMA, /* Domain used for DMA-API */
+ IOMMU_DOMAIN_IDENTITY, /* Identity mapped domain */
+ IOMMU_DOMAIN_UNMANAGED, /* Domain mappings are managed by a third party
+ user (like KVM or VFIO) */
+};
+
struct iommu_domain {
+ enum iommu_domain_type type;
const struct iommu_ops *ops;
void *priv;
iommu_fault_handler_t handler;
@@ -117,7 +126,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)(enum iommu_domain_type);
void (*domain_free)(struct iommu_domain *);
int (*attach_dev)(struct iommu_domain *domain, struct device *dev);
--
1.8.4.5
next prev parent reply other threads:[~2015-01-26 23:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 23:51 [PATCH 00/15] iommu: Move domain allocation into drivers Joerg Roedel
2015-01-26 23:51 ` [PATCH 01/15] iommu: Introduce domain_alloc and domain_free iommu_ops Joerg Roedel
2015-01-26 23:51 ` Joerg Roedel [this message]
2015-01-28 14:19 ` [PATCH 02/15] iommu: Introduce iommu domain types Will Deacon
2015-01-30 12:22 ` Joerg Roedel
2015-01-26 23:51 ` [PATCH 03/15] iommu/amd: Make use of domain_alloc and domain_free Joerg Roedel
2015-01-26 23:51 ` [PATCH 04/15] iommu/vt-d: " Joerg Roedel
2015-01-26 23:51 ` [PATCH 05/15] iommu/omap: " Joerg Roedel
2015-01-26 23:51 ` [PATCH 06/15] iommu/arm-smmu: " Joerg Roedel
2015-01-26 23:51 ` [PATCH 07/15] iommu/exynos: " Joerg Roedel
2015-01-26 23:51 ` [PATCH 08/15] iommu/tegra-smmu: " Joerg Roedel
2015-01-26 23:51 ` [PATCH 09/15] iommu/tegra-gart: " Joerg Roedel
2015-01-26 23:51 ` [PATCH 10/15] iommu/msm: " Joerg Roedel
2015-01-26 23:51 ` [PATCH 11/15] iommu/shmobile: " Joerg Roedel
2015-01-26 23:51 ` [PATCH 12/15] iommu/ipmmu-vmsa: " Joerg Roedel
2015-01-26 23:51 ` [PATCH 13/15] iommu/rockchip: " Joerg Roedel
2015-01-26 23:51 ` [PATCH 14/15] iommu/fsl: " Joerg Roedel
2015-01-26 23:51 ` [PATCH 15/15] iommu: Remove domain_init and domain_free iommu_ops Joerg Roedel
2015-03-20 9:24 ` [PATCH 00/15] iommu: Move domain allocation into drivers Yingjoe Chen
2015-03-23 11:49 ` Joerg Roedel
2015-03-23 13:35 ` Yingjoe Chen
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=1422316305-19216-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).