Commit f2d391c1 authored by Joerg Roedel's avatar Joerg Roedel Committed by Ben Hutchings

iommu/amd: Initialize dma_ops for hotplug and sriov devices

commit ac1534a5 upstream.

When a device is added to the system at runtime the AMD
IOMMU driver initializes the necessary data structures to
handle translation for it. But it forgets to change the
per-device dma_ops to point to the AMD IOMMU driver. So
mapping actually never happens and all DMA accesses end in
an IO_PAGE_FAULT. Fix this.
Reported-by: default avatarStefan Assmann <sassmann@redhat.com>
Signed-off-by: default avatarJoerg Roedel <joerg.roedel@amd.com>
[bwh: Backported to 3.2:
 - Adjust context
 - Use global iommu_pass_through; there is no per-device pass_through]
Signed-off-by: default avatarBen Hutchings <ben@decadent.org.uk>
parent f1796366
......@@ -59,6 +59,8 @@ static struct protection_domain *pt_domain;
static struct iommu_ops amd_iommu_ops;
static struct dma_map_ops amd_iommu_dma_ops;
/*
* general struct to manage commands send to an IOMMU
*/
......@@ -1878,6 +1880,11 @@ static int device_change_notifier(struct notifier_block *nb,
list_add_tail(&dma_domain->list, &iommu_pd_list);
spin_unlock_irqrestore(&iommu_pd_list_lock, flags);
if (!iommu_pass_through)
dev->archdata.dma_ops = &amd_iommu_dma_ops;
else
dev->archdata.dma_ops = &nommu_dma_ops;
break;
case BUS_NOTIFY_DEL_DEVICE:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment