arm64: IOMMU-backed DMA mapping
Subsystems (3)
Robin Murphy
maintainerv4 cover arm64: IOMMU-backed DMA mapping
Hi all,
Here's a quick repost to address feedback on v3, and a couple of other tweaks. Changes this round:
- Fix the heinous dma_mask/coherency confusion, which also simplifies some prototypes and parameter passing as a bonus.
- Reorder the iommu_map/unmap in alloc/free to prevent any potential access the wrong side of clearing/freeing the pages.
- Made the unconditional clearing of allocations a bit more explicit.
- Made the default domain workaround more robust against the possibility of an IOMMU driver giving back the same domain for multiple devices.
Robin.
v3: http://thread.gmane.org/gmane.linux.kernel.iommu/10133
Updated branch at: git://linux-arm.org/linux-rm iommu/dma
Robin Murphy (4):
iommu/iova: Avoid over-allocating when size-aligned
iommu: Implement common IOMMU ops for DMA mapping
arm64: Add IOMMU dma_ops
arm64: Hook up IOMMU dma_ops
arch/arm64/Kconfig | 1 + arch/arm64/include/asm/dma-mapping.h | 15 +- arch/arm64/mm/dma-mapping.c | 452 +++++++++++++++++++++++++++++ drivers/iommu/Kconfig | 7 + drivers/iommu/Makefile | 1 + drivers/iommu/dma-iommu.c | 538 +++++++++++++++++++++++++++++++++++ drivers/iommu/intel-iommu.c | 2 + drivers/iommu/iova.c | 23 +- include/linux/dma-iommu.h | 84 ++++++ include/linux/iommu.h | 1 + 10 files changed, 1099 insertions(+), 25 deletions(-) create mode 100644 drivers/iommu/dma-iommu.c create mode 100644 include/linux/dma-iommu.h
Signature · 1 line
1.9.1
Robin Murphy
maintainerPATCH v4 1/4 iommu/iova: Avoid over-allocating when size-aligned
Currently, allocating a size-aligned IOVA region quietly adjusts the actual allocation size in the process, returning a rounded-up power-of-two-sized allocation. This results in mismatched behaviour in the IOMMU driver if the original size was not a power of two, where the original size is mapped, but the rounded-up IOVA size is unmapped.
Whilst some IOMMUs will happily unmap already-unmapped pages, others consider this an error, so fix it by computing the necessary alignment padding without altering the actual allocation size. Also clean up by making pad_size unsigned, since its callers always pass unsigned values and negative padding makes little sense here anyway.
--- drivers/iommu/intel-iommu.c | 2 ++ drivers/iommu/iova.c | 23 ++++++----------------- 2 files changed, 8 insertions(+), 17 deletions(-)
drivers/iommu/intel-iommu.c +2 -0
@@ -3233,6 +3233,8 @@ static struct iova *intel_alloc_iova(struct device *dev,/* Restrict dma_mask to the width that the iommu can handle */ dma_mask =min_t (uint64_t,DOMAIN_MAX_ADDR (domain->gaw), dma_mask); +/* Ensure we reserve the whole size-aligned region */ + nrpages =__roundup_pow_of_two (nrpages);if (!dmar_forcedac && dma_mask >DMA_BIT_MASK (32 )) {/*
drivers/iommu/iova.c +6 -17
@@ -120,19 +120,14 @@ __cached_rbnode_delete_update(struct iova_domain *iovad, struct iova *free) } } -/* Computes the padding size required, to make the -* the start address naturally aligned on its size +/* +* Computes the padding size required, to make the start address +* naturally aligned on the power-of-two order of its size */ -static int -iova_get_pad_size (int size,unsigned int limit_pfn) +static unsigned int +iova_get_pad_size (unsigned int size,unsigned int limit_pfn) { -unsigned int pad_size =0 ; -unsigned int order =ilog2 (size); - -if (order) - pad_size = (limit_pfn +1 ) % (1 << order); - -return pad_size; +return (limit_pfn +1 - size) & (__roundup_pow_of_two (size) -1 ); } static int __alloc_and_insert_iova_range(struct iova_domain *iovad,
@@ -265,12 +260,6 @@ alloc_iova(struct iova_domain *iovad, unsigned long size,if (!new_iova)return NULL ; -/* If size aligned is set then round the size to -* to next power of two. -*/ -if (size_aligned) - size =__roundup_pow_of_two (size); - ret =__alloc_and_insert_iova_range (iovad, size, limit_pfn, new_iova, size_aligned);
Signature · 1 line
1.9.1
David Woodhouse
AppliedPATCH v4 1/4 iommu/iova: Avoid over-allocating when size-aligned
Quoted 11 lines · Robin Murphy
Currently, allocating a size-aligned IOVA region quietly adjusts the actual allocation size in the process, returning a rounded-up power-of-two-sized allocation. This results in mismatched behaviour in the IOMMU driver if the original size was not a power of two, where the original size is mapped, but the rounded-up IOVA size is unmapped.
Whilst some IOMMUs will happily unmap already-unmapped pages, others consider this an error, so fix it by computing the necessary alignment padding without altering the actual allocation size. Also clean up by making
pad_sizeunsigned, since its callers always pass unsigned values and negative padding makes little sense here anyway.
Applied; thanks.
I'm not 100% sure we *need* the hunk in intel-iommu.c, we can probably live without rounding the size up. It means we'll use huge pages less often, but it's not clear that using them when we didn't *mean* to map the full size of them was the right thing to do in the first place.
But it makes sense to apply the patch as-is, without changing the effective behaviour, and ponder that more deeply later.
Thanks.
Signature · 9 lines
David Woodhouse Open Source Technology Centre David.Woodhouse at intel.com Intel Corporation -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5691 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150728/785b9d33/attachment.bin>
Robin Murphy
maintainerPATCH v4 2/4 iommu: Implement common IOMMU ops for DMA mapping
In reply to Robin MurphyTaking inspiration from the existing arch/arm code, break out some generic functions to interface the DMA-API to the IOMMU-API. This will do the bulk of the heavy lifting for IOMMU-backed dma-mapping.
--- drivers/iommu/Kconfig | 7 + drivers/iommu/Makefile | 1 + drivers/iommu/dma-iommu.c | 538 ++++++++++++++++++++++++++++++++++++++++++++++ include/linux/dma-iommu.h | 84 ++++++++ include/linux/iommu.h | 1 + 5 files changed, 631 insertions(+) create mode 100644 drivers/iommu/dma-iommu.c create mode 100644 include/linux/dma-iommu.h
drivers/iommu/Kconfig +7 -0
@@ -48,6 +48,13 @@ config OF_IOMMU def_bool y depends on OF && IOMMU_API +# IOMMU-agnostic DMA-mapping layer +config IOMMU_DMA + bool + depends on NEED_SG_DMA_LENGTH + select IOMMU_API + select IOMMU_IOVA + config FSL_PAMU bool "Freescale IOMMU support" depends on PPC32
drivers/iommu/Makefile +1 -0
@@ -1,6 +1,7 @@ obj-$(CONFIG_IOMMU_API) += iommu.o obj-$(CONFIG_IOMMU_API) += iommu-traces.o obj-$(CONFIG_IOMMU_API) += iommu-sysfs.o +obj-$(CONFIG_IOMMU_DMA) += dma-iommu.o obj-$(CONFIG_IOMMU_IO_PGTABLE) += io-pgtable.o obj-$(CONFIG_IOMMU_IO_PGTABLE_LPAE) += io-pgtable-arm.o obj-$(CONFIG_IOMMU_IOVA) += iova.o
drivers/iommu/dma-iommu.c new file +538 -0
538 lines not on this page · raw message
include/linux/dma-iommu.h new file +84 -0
84 lines not on this page · raw message
include/linux/iommu.h +1 -0
@@ -81,6 +81,7 @@ struct iommu_domain {iommu_fault_handler_t handler;void *handler_token;struct iommu_domain_geometry geometry; +void *dma_api_cookie; };enum iommu_cap {
Signature · 1 line
1.9.1
Catalin Marinas
maintainerPATCH v4 2/4 iommu: Implement common IOMMU ops for DMA mapping
Quoted 40 lines · Robin Murphy
drivers/iommu/dma-iommu.c new file +40
-0+/** +* iommu_dma_alloc - Allocate and map a buffer contiguous in IOVA space +* @dev: Device to allocate memory for. Must be a real device +* attached to an iommu_dma_domain +* @size: Size of buffer in bytes +* @gfp: Allocation flags +* @prot: IOMMU mapping flags +* @handle: Out argument for allocated DMA handle +* @flush_page: Arch callback to flush a single page from all caches to +* ensure DMA visibility of __GFP_ZERO. May be NULL if not +* required. +* +* If @size is less than PAGE_SIZE, then a full CPU page will be allocated, +* but an IOMMU which supports smaller pages might not map the whole thing. +* +* Return: Array of struct page pointers describing the buffer, +* or NULL on failure. +*/ +struct page **iommu_dma_alloc (struct device *dev,size_t size, +gfp_t gfp,int prot,dma_addr_t *handle, +void (*flush_page)(const void *,phys_addr_t )) +{ +struct iommu_domain *domain =iommu_get_domain_for_dev (dev); +struct iova_domain *iovad = domain->dma_api_cookie; +struct iova *iova; +struct page **pages; +struct sg_table sgt; +dma_addr_t dma_addr; +unsigned int count =PAGE_ALIGN (size) >>PAGE_SHIFT ; + + *handle =DMA_ERROR_CODE ; + + pages =__iommu_dma_alloc_pages (count, gfp); +if (!pages) +return NULL ; + + iova =__alloc_iova (iovad, size, dev->coherent_dma_mask); +if (!iova) + goto out_free_pages; +
drivers/iommu/dma-iommu.c line 302
Quoted 10 lines
drivers/iommu/dma-iommu.c new file +10
-0+ size =iova_align (iovad, size); +if (sg_alloc_table_from_pages (&sgt, pages, count,0 , size,GFP_KERNEL )) + goto out_free_iova; + +if (gfp & __GFP_ZERO) { +struct sg_mapping_iter miter; +/* +* The flushing provided by the SG_MITER_TO_SG flag only +* applies to highmem pages, so it won't do the job here. +*/
The comment here is slightly wrong. The SG_MITER_FROM_SG flushing is done by calling flush_kernel_dcache_page(). This function can be no-op even on architectures implementing highmem. For example, on arm32 it only does some flushing if there is a potential D-cache alias with user space. The flush that you call below is for DMA operations, something entirely different.
drivers/iommu/dma-iommu.c line 305
Quoted 3 lines
drivers/iommu/dma-iommu.c new file +3
-0+sg_miter_start (&miter, sgt.sgl, sgt.orig_nents,SG_MITER_FROM_SG ); +while (sg_miter_next (&miter)) { +memset (miter.addr,0 ,PAGE_SIZE );
Isn't __GFP_ZERO already honoured by alloc_pages in __iommu_dma_alloc_pages?
drivers/iommu/dma-iommu.c line 307
Quoted 2 lines
drivers/iommu/dma-iommu.c new file +2
-0+if (flush_page) +flush_page (miter.addr,page_to_phys (miter.page));
Could you instead do the check as !(prot & IOMEM_CACHE) so that it saves architecture code from passing NULL when coherent?
I'm still not convinced we need this flushing here but I'll follow up in patch 3/4.
Signature · 1 line
Catalin
Robin Murphy
maintainerPATCH v4 3/4 arm64: Add IOMMU dma_ops
In reply to Robin MurphyTaking some inspiration from the arch/arm code, implement the arch-specific side of the DMA mapping ops using the new IOMMU-DMA layer.
Unfortunately the device setup code has to start out as a big ugly mess in order to work usefully right now, as 'proper' operation depends on changes to device probe and DMA configuration ordering, IOMMU groups for platform devices, and default domain support in arm/arm64 IOMMU drivers. The workarounds here need only exist until that work is finished.
--- arch/arm64/mm/dma-mapping.c | 428 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 428 insertions(+)
arch/arm64/mm/dma-mapping.c +428 -0
@@ -526,3 +526,431 @@ static int __init dma_debug_do_init(void)return 0 ; }fs_initcall (dma_debug_do_init); + + +#ifdef CONFIG_IOMMU_DMA +#include <linux/dma-iommu.h> +#include <linux/platform_device.h> +#include <linux/amba/bus.h> + +/* Thankfully, all cache ops are by VA so we can ignore phys here */ +static void flush_page (const void *virt,phys_addr_t phys) +{ +__dma_flush_range (virt, virt +PAGE_SIZE ); +} + +static void *__iommu_alloc_attrs (struct device *dev,size_t size, +dma_addr_t *handle,gfp_t gfp, +struct dma_attrs *attrs) +{ +bool coherent =is_device_dma_coherent (dev); +int ioprot =dma_direction_to_prot (DMA_BIDIRECTIONAL , coherent); +void *addr; + +if (WARN (!dev,"cannot create IOMMU mapping for unknown device\n" )) +return NULL ; + +/* +* Some drivers rely on this, and we may not want to potentially +* expose stale kernel data to devices anyway. +*/ + gfp |= __GFP_ZERO; + +if (gfp & __GFP_WAIT) { +struct page **pages; +pgprot_t pgprot = coherent ?__pgprot (PROT_NORMAL ) : +__pgprot (PROT_NORMAL_NC ); + + pgprot =__get_dma_pgprot (attrs, pgprot, coherent); + pages =iommu_dma_alloc (dev, size, gfp, ioprot, handle, + coherent ?NULL : flush_page); +if (!pages) +return NULL ; + + addr =dma_common_pages_remap (pages, size,VM_USERMAP , pgprot, +__builtin_return_address (0 )); +if (!addr) +iommu_dma_free (dev, pages, size, handle); + }else { +struct page *page; +/* +* In atomic context we can't remap anything, so we'll only +* get the virtually contiguous buffer we need by way of a +* physically contiguous allocation. +*/ +if (coherent) { + page =alloc_pages (gfp,get_order (size)); + addr = page ?page_address (page) :NULL ; + }else { + addr =__alloc_from_pool (size, &page, gfp); + } +if (!addr) +return NULL ; + + *handle =iommu_dma_map_page (dev, page,0 , size, ioprot); +if (iommu_dma_mapping_error (dev, *handle)) { +if (coherent) +__free_pages (page,get_order (size)); +else +__free_from_pool (addr, size); + addr =NULL ; + } + } +return addr; +} + +static void __iommu_free_attrs (struct device *dev,size_t size,void *cpu_addr, +dma_addr_t handle,struct dma_attrs *attrs) +{ +/* +* @cpu_addr will be one of 3 things depending on how it was allocated: +* - A remapped array of pages from iommu_dma_alloc(), for all +* non-atomic allocations. +* - A non-cacheable alias from the atomic pool, for atomic +* allocations by non-coherent devices. +* - A normal lowmem address, for atomic allocations by +* coherent devices. +* Hence how dodgy the below logic looks... +*/ +if (__in_atomic_pool (cpu_addr, size)) { +iommu_dma_unmap_page (dev, handle, size,0 ,NULL ); +__free_from_pool (cpu_addr, size); + }else if (is_vmalloc_addr (cpu_addr)){ +struct vm_struct *area =find_vm_area (cpu_addr); + +if (WARN_ON (!area || !area->pages)) +return ; +iommu_dma_free (dev, area->pages, size, &handle); +dma_common_free_remap (cpu_addr, size,VM_USERMAP ); + }else { +iommu_dma_unmap_page (dev, handle, size,0 ,NULL ); +__free_pages (virt_to_page (cpu_addr),get_order (size)); + } +} + +static int __iommu_mmap_attrs (struct device *dev,struct vm_area_struct *vma, +void *cpu_addr,dma_addr_t dma_addr,size_t size, +struct dma_attrs *attrs) +{ +struct vm_struct *area; +int ret; + + vma->vm_page_prot =__get_dma_pgprot (attrs, vma->vm_page_prot, +is_device_dma_coherent (dev)); + +if (dma_mmap_from_coherent (dev, vma, cpu_addr, size, &ret)) +return ret; + + area =find_vm_area (cpu_addr); +if (WARN_ON (!area || !area->pages)) +return -ENXIO ; + +return iommu_dma_mmap (area->pages, size, vma); +} + +static int __iommu_get_sgtable (struct device *dev,struct sg_table *sgt, +void *cpu_addr,dma_addr_t dma_addr, +size_t size,struct dma_attrs *attrs) +{ +unsigned int count =PAGE_ALIGN (size) >>PAGE_SHIFT ; +struct vm_struct *area =find_vm_area (cpu_addr); + +if (WARN_ON (!area || !area->pages)) +return -ENXIO ; + +return sg_alloc_table_from_pages (sgt, area->pages, count,0 , size, +GFP_KERNEL ); +} + +static void __iommu_sync_single_for_cpu (struct device *dev, +dma_addr_t dev_addr,size_t size, +enum dma_data_direction dir) +{ +phys_addr_t phys; + +if (is_device_dma_coherent (dev)) +return ; + + phys =iommu_iova_to_phys (iommu_get_domain_for_dev (dev), dev_addr); +__dma_unmap_area (phys_to_virt (phys), size, dir); +} + +static void __iommu_sync_single_for_device (struct device *dev, +dma_addr_t dev_addr,size_t size, +enum dma_data_direction dir) +{ +phys_addr_t phys; + +if (is_device_dma_coherent (dev)) +return ; + + phys =iommu_iova_to_phys (iommu_get_domain_for_dev (dev), dev_addr); +__dma_map_area (phys_to_virt (phys), size, dir); +} + +static dma_addr_t __iommu_map_page (struct device *dev,struct page *page, +unsigned long offset,size_t size, +enum dma_data_direction dir, +struct dma_attrs *attrs) +{ +bool coherent =is_device_dma_coherent (dev); +int prot =dma_direction_to_prot (dir, coherent); +dma_addr_t dev_addr =iommu_dma_map_page (dev, page, offset, size, prot); + +if (!iommu_dma_mapping_error (dev, dev_addr) && + !dma_get_attr (DMA_ATTR_SKIP_CPU_SYNC , attrs)) +__iommu_sync_single_for_device (dev, dev_addr, size, dir); + +return dev_addr; +} + +static void __iommu_unmap_page (struct device *dev,dma_addr_t dev_addr, +size_t size,enum dma_data_direction dir, +struct dma_attrs *attrs) +{ +if (!dma_get_attr (DMA_ATTR_SKIP_CPU_SYNC , attrs)) +__iommu_sync_single_for_cpu (dev, dev_addr, size, dir); + +iommu_dma_unmap_page (dev, dev_addr, size, dir, attrs); +} + +static void __iommu_sync_sg_for_cpu (struct device *dev, +struct scatterlist *sgl,int nelems, +enum dma_data_direction dir) +{ +struct scatterlist *sg; +int i; + +if (is_device_dma_coherent (dev)) +return ; + +for_each_sg (sgl, sg, nelems, i) +__dma_unmap_area (sg_virt (sg), sg->length, dir); +} + +static void __iommu_sync_sg_for_device (struct device *dev, +struct scatterlist *sgl,int nelems, +enum dma_data_direction dir) +{ +struct scatterlist *sg; +int i; + +if (is_device_dma_coherent (dev)) +return ; + +for_each_sg (sgl, sg, nelems, i) +__dma_map_area (sg_virt (sg), sg->length, dir); +} + +static int __iommu_map_sg_attrs (struct device *dev,struct scatterlist *sgl, +int nelems,enum dma_data_direction dir, +struct dma_attrs *attrs) +{ +bool coherent =is_device_dma_coherent (dev); + +if (!dma_get_attr (DMA_ATTR_SKIP_CPU_SYNC , attrs)) +__iommu_sync_sg_for_device (dev, sgl, nelems, dir); + +return iommu_dma_map_sg (dev, sgl, nelems, +dma_direction_to_prot (dir, coherent)); +} + +static void __iommu_unmap_sg_attrs (struct device *dev, +struct scatterlist *sgl,int nelems, +enum dma_data_direction dir, +struct dma_attrs *attrs) +{ +if (!dma_get_attr (DMA_ATTR_SKIP_CPU_SYNC , attrs)) +__iommu_sync_sg_for_cpu (dev, sgl, nelems, dir); + +iommu_dma_unmap_sg (dev, sgl, nelems, dir, attrs); +} + +static struct dma_map_ops iommu_dma_ops = { + .alloc = __iommu_alloc_attrs, + .free = __iommu_free_attrs, + .mmap = __iommu_mmap_attrs, + .get_sgtable = __iommu_get_sgtable, + .map_page = __iommu_map_page, + .unmap_page = __iommu_unmap_page, + .map_sg = __iommu_map_sg_attrs, + .unmap_sg = __iommu_unmap_sg_attrs, + .sync_single_for_cpu = __iommu_sync_single_for_cpu, + .sync_single_for_device = __iommu_sync_single_for_device, + .sync_sg_for_cpu = __iommu_sync_sg_for_cpu, + .sync_sg_for_device = __iommu_sync_sg_for_device, + .dma_supported = iommu_dma_supported, + .mapping_error = iommu_dma_mapping_error, +}; + +/* +* TODO: Right now __iommu_setup_dma_ops() gets called too early to do +* everything it needs to - the device isn't yet fully created, and the +* IOMMU driver hasn't seen it yet, so we need this delayed attachment +* dance. Once IOMMU probe ordering is sorted to move the +* arch_setup_dma_ops() call later, all the notifier bits below become +* unnecessary, and will go away. +*/ +struct iommu_dma_notifier_data { +struct list_head list; +struct device *dev; +struct iommu_domain *dma_domain; +}; +static LIST_HEAD (iommu_dma_masters); +static DEFINE_MUTEX (iommu_dma_notifier_lock); + +static int __iommu_attach_notifier (struct notifier_block *nb, +unsigned long action,void *data) +{ +struct iommu_dma_notifier_data *master, *tmp; + +if (action !=BUS_NOTIFY_ADD_DEVICE ) +return 0 ; +/* +* We expect the list to only contain the most recent addition +* (which should be the same device as in @data) so just process +* the whole thing blindly. If any previous attachments did happen +* to fail, they get a free retry since the domains are still live. +*/ +mutex_lock (&iommu_dma_notifier_lock); +list_for_each_entry_safe (master, tmp, &iommu_dma_masters, list) { +if (iommu_attach_device (master->dma_domain, master->dev)) { +pr_warn ("Failed to attach device %s to IOMMU mapping; retaining platform DMA ops\n" , +dev_name (master->dev)); + }else { + master->dev->archdata.dma_ops = &iommu_dma_ops; +list_del (&master->list); +kfree (master); + } + } +mutex_unlock (&iommu_dma_notifier_lock); +return 0 ; +} + +static int register_iommu_dma_ops_notifier (struct bus_type *bus) +{ +int ret; +struct notifier_block *nb =kzalloc (sizeof (*nb),GFP_KERNEL ); + +/* +* The device must be attached to a domain before the driver probe +* routine gets a chance to start allocating DMA buffers. However, +* the IOMMU driver also needs a chance to configure the iommu_group +* via its add_device callback first, so we need to make the attach +* happen between those two points. Since the IOMMU core uses a bus +* notifier with default priority for add_device, do the same but +* with a lower priority to ensure the appropriate ordering. +*/ + nb->notifier_call = __iommu_attach_notifier; + nb->priority =-100 ; + + ret =bus_register_notifier (bus, nb); +if (ret) { +pr_warn ("Failed to register DMA domain notifier; IOMMU DMA ops unavailable on bus '%s'\n" , + bus->name); +kfree (nb); + } +return ret; +} + +static int queue_iommu_attach (struct iommu_domain *domain,struct device *dev) +{ +struct iommu_dma_notifier_data *iommudata =NULL ; + + iommudata =kzalloc (sizeof (*iommudata),GFP_KERNEL ); +if (!iommudata) +return -ENOMEM ; + + iommudata->dev = dev; + iommudata->dma_domain = domain; + +mutex_lock (&iommu_dma_notifier_lock); +list_add (&iommudata->list, &iommu_dma_masters); +mutex_unlock (&iommu_dma_notifier_lock); +return 0 ; +} + +static int __init arm64_iommu_dma_init (void ) +{ +int ret; + + ret =iommu_dma_init (); +if (!ret) + ret =register_iommu_dma_ops_notifier (&platform_bus_type); +if (!ret) + ret =register_iommu_dma_ops_notifier (&amba_bustype); +return ret; +} +arch_initcall (arm64_iommu_dma_init); + +/* Hijack some domain feature flags for the stop-gap meddling below */ +#define __IOMMU_DOMAIN_ARM64 (1U << 31) +#define __IOMMU_DOMAIN_ARM64_IOVA (1U << 30) + +static void __iommu_setup_dma_ops (struct device *dev,u64 dma_base,u64 size, +const struct iommu_ops *ops) +{ +struct iommu_domain *domain; +int err; + +if (!ops) +return ; +/* +* In a perfect world, everything happened in the right order up to +* here, and the IOMMU core has already attached the device to an +* appropriate default domain for us to set up... +*/ + domain =iommu_get_domain_for_dev (dev); +if (!domain) { +/* +* Urgh. Reliable default domains for platform devices can't +* happen anyway without some sensible way of handling +* non-trivial groups. So until then, HORRIBLE HACKS! +*/ + domain = ops->domain_alloc (IOMMU_DOMAIN_DMA ); +if (!domain) + domain = ops->domain_alloc (IOMMU_DOMAIN_UNMANAGED ); +if (!domain) + goto out_no_domain; + + domain->ops = ops; + domain->type =IOMMU_DOMAIN_DMA | __IOMMU_DOMAIN_ARM64; +if (!domain->dma_api_cookie) { + domain->type |= __IOMMU_DOMAIN_ARM64_IOVA; +if (iommu_get_dma_cookie (domain)) + goto out_put_domain; + } + } + +if (iommu_dma_init_domain (domain, dma_base, size)) { +pr_warn ("Failed to create %llu-byte IOMMU mapping for device %s\n" , + size,dev_name (dev)); + goto out_put_domain; + } + +if (dev->iommu_group) + err =iommu_attach_device (domain, dev); +else + err =queue_iommu_attach (domain, dev); + +if (!err) { + dev->archdata.dma_ops = &iommu_dma_ops; +return ; + } + +out_put_domain: +if (domain->type & __IOMMU_DOMAIN_ARM64_IOVA) +iommu_put_dma_cookie (domain); +if (domain->type & __IOMMU_DOMAIN_ARM64) + ops->domain_free (domain); +out_no_domain: +pr_warn ("Failed to set up IOMMU domain for device %s\n" ,dev_name (dev)); +} + +#else + +static void __iommu_setup_dma_ops (struct device *dev,u64 dma_base,u64 size, +struct iommu_ops *iommu) +{ } + +#endif /* CONFIG_IOMMU_DMA */
Signature · 1 line
1.9.1
Catalin Marinas
maintainerPATCH v4 3/4 arm64: Add IOMMU dma_ops
Quoted 13 lines · Robin Murphy
arch/arm64/mm/dma-mapping.c +13
-0+static void *__iommu_alloc_attrs (struct device *dev,size_t size, +dma_addr_t *handle,gfp_t gfp, +struct dma_attrs *attrs) +{ +bool coherent =is_device_dma_coherent (dev); +int ioprot =dma_direction_to_prot (DMA_BIDIRECTIONAL , coherent); +void *addr; + +if (WARN (!dev,"cannot create IOMMU mapping for unknown device\n" )) +return NULL ; + +/* +* Some drivers rely on this, and we may not want to potentially
arch/arm64/mm/dma-mapping.c static int __init dma_debug_do_init(void) · line 564
Quoted 10 lines
arch/arm64/mm/dma-mapping.c +10
-0+* expose stale kernel data to devices anyway. +*/ + gfp |= __GFP_ZERO; + +if (gfp & __GFP_WAIT) { +struct page **pages; +pgprot_t pgprot = coherent ?__pgprot (PROT_NORMAL ) : +__pgprot (PROT_NORMAL_NC ); + + pgprot =__get_dma_pgprot (attrs, pgprot, coherent);
I think you can simplify this:
pgprot_t pgprot = __get_dma_pgprot(attrs, PAGE_KERNEL, coherent);
(and we could do the same in __dma_alloc)
arch/arm64/mm/dma-mapping.c static int __init dma_debug_do_init(void) · line 566
Quoted 2 lines
arch/arm64/mm/dma-mapping.c +2
-0+ pages =iommu_dma_alloc (dev, size, gfp, ioprot, handle, + coherent ?NULL : flush_page);
I commented on patch 2/4. If we checked for IOMMU_CACHE in iommu_dma_alloc(), we could always pass flush_page here without the NULL.
arch/arm64/mm/dma-mapping.c static int __init dma_debug_do_init(void) · line 573
Quoted 7 lines
arch/arm64/mm/dma-mapping.c +7
-0+if (!pages) +return NULL ; + + addr =dma_common_pages_remap (pages, size,VM_USERMAP , pgprot, +__builtin_return_address (0 )); +if (!addr) +iommu_dma_free (dev, pages, size, handle);
For arm64, it would have been easier to simply flush the caches here and avoid the flush_page argument. However, I reread your earlier reply, so if we ever honour the ATTR_NO_KERNEL_MAPPING, then we would have to iterate over the individual pages in the arch code. Let's leave it as per your patch 2/4 (with a flush_page argument).
Signature · 1 line
Catalin
Robin Murphy
maintainerPATCH v4 4/4 arm64: Hook up IOMMU dma_ops
In reply to Robin MurphyWith iommu_dma_ops in place, hook them up to the configuration code, so IOMMU-fronted devices will get them automatically.
--- arch/arm64/Kconfig | 1 + arch/arm64/include/asm/dma-mapping.h | 15 +++++++-------- arch/arm64/mm/dma-mapping.c | 24 ++++++++++++++++++++++++ 3 files changed, 32 insertions(+), 8 deletions(-)
arch/arm64/Kconfig +1 -0
@@ -72,6 +72,7 @@ config ARM64 select HAVE_PERF_USER_STACK_DUMP select HAVE_RCU_TABLE_FREE select HAVE_SYSCALL_TRACEPOINTS + select IOMMU_DMA if IOMMU_SUPPORT select IRQ_DOMAIN select IRQ_FORCED_THREADING select MODULES_USE_ELF_RELA
arch/arm64/include/asm/dma-mapping.h +7 -8
@@ -56,16 +56,15 @@ static inline struct dma_map_ops *get_dma_ops(struct device *dev)return __generic_dma_ops (dev); } -static inline void arch_setup_dma_ops (struct device *dev,u64 dma_base,u64 size, -struct iommu_ops *iommu,bool coherent) -{ -if (!acpi_disabled && !dev->archdata.dma_ops) - dev->archdata.dma_ops = dma_ops; - - dev->archdata.dma_coherent = coherent; -} +void arch_setup_dma_ops (struct device *dev,u64 dma_base,u64 size, +struct iommu_ops *iommu,bool coherent);#define arch_setup_dma_ops arch_setup_dma_ops +#ifdef CONFIG_IOMMU_DMA +void arch_teardown_dma_ops (struct device *dev); +#define arch_teardown_dma_ops arch_teardown_dma_ops +#endif +/* do not use this function in a driver */ static inline bool is_device_dma_coherent (struct device *dev) {
arch/arm64/mm/dma-mapping.c +24 -0
@@ -947,6 +947,20 @@ out_no_domain:pr_warn ("Failed to set up IOMMU domain for device %s\n" ,dev_name (dev)); } +void arch_teardown_dma_ops (struct device *dev) +{ +struct iommu_domain *domain =iommu_get_domain_for_dev (dev); + +if (domain) { +iommu_detach_device (domain, dev); +if (domain->type & __IOMMU_DOMAIN_ARM64_IOVA) +iommu_put_dma_cookie (domain); +if (domain->type & __IOMMU_DOMAIN_ARM64) +iommu_domain_free (domain); + dev->archdata.dma_ops =NULL ; + } +} +#else static void __iommu_setup_dma_ops(struct device *dev, u64 dma_base, u64 size,
@@ -954,3 +968,13 @@ static void __iommu_setup_dma_ops(struct device *dev, u64 dma_base, u64 size, { }#endif /* CONFIG_IOMMU_DMA */ + +void arch_setup_dma_ops (struct device *dev,u64 dma_base,u64 size, +struct iommu_ops *iommu,bool coherent) +{ +if (!acpi_disabled && !dev->archdata.dma_ops) + dev->archdata.dma_ops = dma_ops; + + dev->archdata.dma_coherent = coherent; +__iommu_setup_dma_ops (dev, dma_base, size, iommu); +}
Signature · 1 line
1.9.1
Catalin Marinas
maintainerPATCH v4 4/4 arm64: Hook up IOMMU dma_ops
Quoted 4 lines · Robin Murphy
With
iommu_dma_opsin place, hook them up to the configuration code, so IOMMU-fronted devices will get them automatically.Signed-off-by Robin Murphy <[email protected]>
Joerg Roedel
maintainerv4 cover arm64: IOMMU-backed DMA mapping
In reply to Robin MurphyQuoted 3 lines · Robin Murphy
arch/arm64/Kconfig | 1 + arch/arm64/include/asm/dma-mapping.h | 15 +- arch/arm64/mm/dma-mapping.c | 452 +++++++++++++++++++++++++++++
What happened to the plan to merge this with the existing iommu-based dma-api implementation for 32 bit ARM?
Joerg
Robin Murphy
maintainerv4 cover arm64: IOMMU-backed DMA mapping
Hi Joerg,
Quoted 7 lines · Joerg Roedel
Quoted 3 lines · Robin Murphy
arch/arm64/Kconfig | 1 + arch/arm64/include/asm/dma-mapping.h | 15 +- arch/arm64/mm/dma-mapping.c | 452 +++++++++++++++++++++++++++++What happened to the plan to merge this with the existing iommu-based dma-api implementation for 32 bit ARM?
The issue currently is that there are a bunch of drivers using the exported arm_iommu_* functions directly. From what I can tell, they seem like they could probably all be converted to using default domains and/or the new domain type abstractions via the core IOMMU API, which would then allow killing off dma_iommu_mapping and rewriting the arch/arm implementation to use the new shared code. I don't currently have any 32-bit platform to test with, so I'm a little dubious of taking that all on myself right now.
In the meantime on arm64, DMA mapping ops are needed for SMMUv3 platform device support, the Mediatek M4U patches and my own SMMUv2 work, so it would be very useful to get the arm64 and common code in as a first step, then look at cleaning up arch/arm for 4.4 without dangling dependencies.
Robin.
Quoted 4 lines
Joerg
v4 cover arm64: IOMMU-backed DMA mapping
Hi Joerg, Robin,
Quoted 18 lines · Robin Murphy
Quoted 7 lines · Joerg Roedel
Quoted 3 lines · Robin Murphy
arch/arm64/Kconfig | 1 + arch/arm64/include/asm/dma-mapping.h | 15 +- arch/arm64/mm/dma-mapping.c | 452 +++++++++++++++++++++++++++++What happened to the plan to merge this with the existing iommu-based dma-api implementation for 32 bit ARM?
The issue currently is that there are a bunch of drivers using the exported arm_iommu_* functions directly. From what I can tell, they seem like they could probably all be converted to using default domains and/or the new domain type abstractions via the core IOMMU API, which would then allow killing off
dma_iommu_mappingand rewriting thearch/armimplementation to use the new shared code. I don't currently have any 32-bit platform to test with, so I'm a little dubious of taking that all on myself right now.
Quoted 5 lines
In the meantime on arm64, DMA mapping ops are needed for SMMUv3 platform device support, the Mediatek M4U patches and my own SMMUv2 work, so it would be very useful to get the arm64 and common code in as a first step, then look at cleaning up
arch/armfor 4.4 without dangling dependencies.
What's the plan with this? Do we need to port 32-bit ARM before it's a candidate for merging, or can we push ahead with getting this up and running for arm64 (which currently can't use an IOMMU for DMA)?
Will