bd421264ed
The IOMMU core code has support for deferring the attachment of a domain
to a device. This is needed in kdump kernels where the new domain must
not be attached to a device before the device driver takes it over.
When the AMD IOMMU driver got converted to use the dma-iommu
implementation, the deferred attaching got lost. The code in
dma-iommu.c has support for deferred attaching, but it calls into
iommu_attach_device() to actually do it. But iommu_attach_device()
will check if the device should be deferred in it code-path and do
nothing, breaking deferred attachment.
Move the is_deferred_attach() check out of the attach_device path and
into iommu_group_add_device() to make deferred attaching work from the
dma-iommu code.
Fixes:
|
||
---|---|---|
.. | ||
Kconfig | ||
Makefile | ||
amd_iommu.c | ||
amd_iommu.h | ||
amd_iommu_debugfs.c | ||
amd_iommu_init.c | ||
amd_iommu_proto.h | ||
amd_iommu_quirks.c | ||
amd_iommu_types.h | ||
amd_iommu_v2.c | ||
arm-smmu-impl.c | ||
arm-smmu-qcom.c | ||
arm-smmu-v3.c | ||
arm-smmu.c | ||
arm-smmu.h | ||
dma-iommu.c | ||
dmar.c | ||
exynos-iommu.c | ||
fsl_pamu.c | ||
fsl_pamu.h | ||
fsl_pamu_domain.c | ||
fsl_pamu_domain.h | ||
hyperv-iommu.c | ||
intel-iommu-debugfs.c | ||
intel-iommu.c | ||
intel-pasid.c | ||
intel-pasid.h | ||
intel-svm.c | ||
intel-trace.c | ||
intel_irq_remapping.c | ||
io-pgtable-arm-v7s.c | ||
io-pgtable-arm.c | ||
io-pgtable.c | ||
ioasid.c | ||
iommu-debugfs.c | ||
iommu-sysfs.c | ||
iommu-traces.c | ||
iommu.c | ||
iova.c | ||
ipmmu-vmsa.c | ||
irq_remapping.c | ||
irq_remapping.h | ||
msm_iommu.c | ||
msm_iommu.h | ||
msm_iommu_hw-8xxx.h | ||
mtk_iommu.c | ||
mtk_iommu.h | ||
mtk_iommu_v1.c | ||
of_iommu.c | ||
omap-iommu-debug.c | ||
omap-iommu.c | ||
omap-iommu.h | ||
omap-iopgtable.h | ||
qcom_iommu.c | ||
rockchip-iommu.c | ||
s390-iommu.c | ||
tegra-gart.c | ||
tegra-smmu.c | ||
virtio-iommu.c |