Skip to content

iommu/vt-d: Keep RMRR mappings around on driver unbind

Joerg Roedel linux-iommu lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 10 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2driver core: Add BUS_NOTIFY_REMOVED_DEVICE eventdrivers/base/core.c include/linux/device.h+9 -50 replies
2/2iommu/vt-d: Only remove domain when device is removeddrivers/iommu/intel-iommu.c+1 -107 replies

Reviews trailers per patch

None of the 2 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchGreg Kroah-HartmanJerry Hoemann
SeriesA-b T-b
1/2
2/2

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/2] iommu/vt-d: Keep RMRR mappings around on driver unbind

Hi,

here is a patch-set to fix an issue recently discovered when the Intel IOMMU is in use with devices that need RMRR mappings.

The problem is that the RMRR mappings are destroyed when the device driver is unbound from the device, causing DMAR faults.

To solve this problem a device driver core change is necessary to catch the right point in time for the IOMMU code to destroy any mappings for a device.

With this patch-set the RMRR mappings are only destroyed when the device is actually removed from the system.

Please review.

Thanks,

Joerg

Joerg Roedel (2):
driver core: Add BUS_NOTIFY_REMOVED_DEVICE event iommu/vt-d: Only remove domain when device is removed

 drivers/base/core.c         |  3 +++
 drivers/iommu/intel-iommu.c | 11 +----------
 include/linux/device.h      | 11 ++++++-----
 3 files changed, 10 insertions(+), 15 deletions(-)
Signature · 1 line
1.9.1