Re: [PATCH v4 1/1] iommu-api: Add map_sg/unmap_sg functions

Hi Olav, On Fri, Aug 01, 2014 at 01:54:44AM +0100, Olav Haugan wrote: Mapping and unmapping are more often than not in the critical path. map_sg and unmap_sg allows IOMMU driver implementations to optimize the process of mapping and unmapping buffers into the IOMMU page tables. Instead of

[PATCH 2/2] iommu: Implement a dummy bus_set_iommu()

From: Thierry Reding tred...@nvidia.com This allows IOMMU drivers to compile even if IOMMU_API is not selected and helps improve compile coverage. Signed-off-by: Thierry Reding tred...@nvidia.com --- include/linux/iommu.h | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH 1/2] iommu: Always define struct iommu_ops

From: Thierry Reding tred...@nvidia.com With this structure always defined, drivers can be always compiled, irrespective of whether or not IOMMU_API is enabled. This helps to increase compile coverage without having to build with two separate configurations. Unused code can still be discarded by

Re: [PATCH v4 1/1] iommu-api: Add map_sg/unmap_sg functions

Hi Will, On 8/1/2014 1:22 AM, Will Deacon wrote: Hi Olav, On Fri, Aug 01, 2014 at 01:54:44AM +0100, Olav Haugan wrote: Mapping and unmapping are more often than not in the critical path. map_sg and unmap_sg allows IOMMU driver implementations to optimize the process of mapping and

[PATCH] iommu/amd: Implement syscore_ops.shutdown()

During hibernation or shutdown, AMD iommu generates warnings on some platforms as below: [ 89.089832] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:12.0 domain=0x0009 address=0x0080 flags=0x0020] [ 89.102239] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:12.0 domain=0x0009