iommu/vt-d: Keep RMRR mappings around on driver unbind
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 10 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | driver core: Add BUS_NOTIFY_REMOVED_DEVICE eventdrivers/ include/ | +9 | 0 replies | |
| 2/2 | iommu/vt-d: Only remove domain when device is removeddrivers/ | +1 | 7 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.
| Patch | Greg Kroah-Hartman | Jerry Hoemann |
|---|---|---|
| Series | A-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.
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