Hi,

as David Woodhouse pointed out, my fixes and cleanups for
the original patch-set turned out to be a complete rewrite.
So to have a cleaner history of the feature and to make
backporting easier, here is a rewrite of my changes based on
v4.1-rc7.

Some additional issues have been fixed by this rewrite, like
a kdump-kernel boot panic with 'iommu=pt' and support for
copying the extended root-entry and context table formats
has been added.

I plan to rebuild the x86/vt-d branch of the iommu tree with
these patches.

Regards,

        Joerg

Joerg Roedel (19):
  iommu/vt-d: Cleanup log messages
  iommu/vt-d: Init QI before root entry is allocated
  iommu/vt-d: Make root entry visible for hardware right after
    allocation
  iommu/vt-d: Detect pre enabled translation
  iommu/vt-d: Copy translation tables from old kernel
  iommu/vt-d: Do not re-use domain-ids from the old kernel
  iommu/vt-d: Mark copied context entries
  iommu/vt-d: Allocate si_domain in init_dmars()
  iommu/vt-d: Don't do early domain assignment if kdump kernel
  iommu/vt-d: Don't copy translation tables if RTT bit needs to be
    changed
  iommu/vt-d: Don't disable translation prior to OS handover
  iommu/vt-d: Enable Translation only if it was previously disabled
  iommu/vt-d: Move EIM detection to intel_prepare_irq_remapping
  iommu/vt-d: Move QI initializationt to intel_setup_irq_remapping
  iommu/vt-d: Disable IRQ remapping in intel_prepare_irq_remapping
  iommu/vt-d: Set IRTA in intel_setup_irq_remapping
  iommu/vt-d: Copy IR table from old kernel when in kdump mode
  iommu/vt-d: Make sure copied over IR entries are not reused
  iommu/vt-d: Don't disable IR when it was previously enabled

 drivers/iommu/dmar.c                |  28 +-
 drivers/iommu/intel-iommu.c         | 495 ++++++++++++++++++++++++++++--------
 drivers/iommu/intel_irq_remapping.c | 255 ++++++++++++-------
 include/linux/intel-iommu.h         |   5 +
 4 files changed, 573 insertions(+), 210 deletions(-)

-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to