Suresh Siddha c2c7286ac6 intr_remap: Call dmar_dev_scope_init() explicitly ... Both DMA-remapping aswell as Interrupt-remapping depend on the dmar dev scope to be initialized. When both DMA and IRQ-remapping are enabled, we depend on DMA-remapping init code to call dmar_dev_scope_init(). This resulted in not doing this init when DMA-remapping was turned off but interrupt-remapping turned on in the kernel config. This caused interrupt routing to break with CONFIG_INTR_REMAP=y and CONFIG_DMAR=n. This issue was introduced by this commit: | commit 9d5ce73a64 | Author: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> | Date: Tue Nov 10 19:46:16 2009 +0900 | | x86: intel-iommu: Convert detect_intel_iommu to use iommu_init hook Fix this by calling dmar_dev_scope_init() explicitly from the interrupt remapping code too. Reported-by: Andrew Vasquez <andrew.vasquez@qlogic.com> Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com> Cc: yinghai@kernel.org Cc: youquan.song@intel.com Cc: joerg.roedel@amd.com Cc: tony.luck@intel.com Cc: dwmw2@infradead.org Link: http://lkml.kernel.org/r/20110824001456.229207526@sbsiddha-desk.sc.intel.com Signed-off-by: Ingo Molnar <mingo@elte.hu>		2011-09-21 10:21:52 +02:00
..
amd_iommu_init.c
amd_iommu_proto.h
amd_iommu_types.h
amd_iommu.c	iommu/amd: Don't take domain->lock recursivly	2011-09-02 14:19:50 +02:00
dmar.c	intr_remap: Call dmar_dev_scope_init() explicitly	2011-09-21 10:21:52 +02:00
intel-iommu.c	intr_remap: Call dmar_dev_scope_init() explicitly	2011-09-21 10:21:52 +02:00
intr_remapping.c	intr_remap: Call dmar_dev_scope_init() explicitly	2011-09-21 10:21:52 +02:00
intr_remapping.h
iommu.c
iova.c
Kconfig
Makefile
msm_iommu_dev.c
msm_iommu.c