[lkml]   [2019]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH v2 0/7] iommu/vt-d: Fix-up device-domain relationship by refactoring to use iommu group default domain.
Patches 1 and 2 are the same as v1.

Refactored ISA direct mappings to be returned by iommu_get_resv_regions.
Integrated patch by Lu to defer turning on DMAR until iommu.c has mapped
reserved regions.
Integrated patches by Lu to remove more unused code in cleanup.

Lu: I didn't integrate your patch to set the default domain type as it
isn't directly related to the aim of this patchset. Instead patch 4
addresses the issue of a device requiring an identity domain by ignoring
the domain param in attach_device and printing a warning.

I booted some of our devices with this patchset and haven't seen any
issues. It doesn't look like we have any devices with RMRR's though so
those codepaths aren't tested.

James Sewart (7):
iommu: Move iommu_group_create_direct_mappings to after device_attach
iommu/vt-d: Implement apply_resv_region for reserving IOVA ranges
iommu/vt-d: Expose ISA direct mapping region via
iommu/vt-d: Ignore domain parameter in attach_device if device
requires identity map
iommu/vt-d: Allow IOMMU_DOMAIN_DMA to be allocated by iommu_ops
iommu/vt-d: Remove lazy allocation of domains

Lu Baolu (1):
iommu/vt-d: Enable DMA remapping after rmrr mapped

drivers/iommu/intel-iommu.c | 444 +++++++++++-------------------------
drivers/iommu/iommu.c | 4 +-
2 files changed, 131 insertions(+), 317 deletions(-)


 \ /
  Last update: 2019-03-14 12:58    [W:0.241 / U:1.404 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site