[PATCH] interrupt remapping: Fix interrupt remapping hang if interrupt remapping disable in BIOS

From: Youquan Song
Date: Mon Sep 07 2009 - 03:14:39 EST

BIOS clear DMAR table INTR_REMAP flag to disable interrupt remapping. Current
kernel only check interrupt remapping(IR) flag in DRHD's extended capability
register to decide interrupt remapping support or not. But IR flag will not
affected by BIOS setting.

So though BIOS disable interrupt remapping feature, However,
intr_remapping_supported function will report interrupt supported. On this
cases, it will continue to enable interrupt remapping which will cause kernel
hang. This bug exist on almost platform support interrupt remapping.

This patch add DMAR table INTR_REMAP flag check before enable interrup remapping

Signed-off-by: Youquan, Song <youquan.song@xxxxxxxxx>

diff --git a/drivers/pci/dmar.c b/drivers/pci/dmar.c
index a8a4383..78f4ca8 100644
--- a/drivers/pci/dmar.c
+++ b/drivers/pci/dmar.c
@@ -43,7 +43,7 @@

-static struct acpi_table_header * __initdata dmar_tbl;
+struct acpi_table_header * __initdata dmar_tbl;
static acpi_size dmar_tbl_size;

static void __init dmar_register_drhd_unit(struct dmar_drhd_unit *drhd)
diff --git a/drivers/pci/intr_remapping.c b/drivers/pci/intr_remapping.c
index ebfa47b..97d1561 100644
--- a/drivers/pci/intr_remapping.c
+++ b/drivers/pci/intr_remapping.c
@@ -16,6 +16,7 @@
static struct ioapic_scope ir_ioapic[MAX_IO_APICS];
static int ir_ioapic_num;
int intr_remapping_enabled;
+extern struct acpi_table_header *__initdata dmar_tbl;

static int disable_intremap;
static __init int setup_nointremap(char *str)
@@ -607,9 +608,14 @@ end:
int __init intr_remapping_supported(void)
struct dmar_drhd_unit *drhd;
+ struct acpi_table_dmar *dmar;
if (disable_intremap)
return 0;
+ dmar = (struct acpi_table_dmar *)dmar_tbl;
+ if (!(dmar->flags & 0x1))
+ return 0;

for_each_drhd_unit(drhd) {
struct intel_iommu *iommu = drhd->iommu;
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/