summaryrefslogtreecommitdiffstats
path: root/arch/x86/pci
diff options
context:
space:
mode:
authorKeith Busch <keith.busch@intel.com>2016-06-17 16:00:21 -0600
committerThomas Gleixner <tglx@linutronix.de>2016-06-18 10:00:55 +0200
commit30ce0350381351646ef86b64e6d3840b3869833b (patch)
treee8322f6fbecf89342036ca77d74454ab2a3f73c5 /arch/x86/pci
parentedd14cfebc4404698544d407ecf8eda6e19aa19e (diff)
downloadlinux-30ce0350381351646ef86b64e6d3840b3869833b.tar.gz
linux-30ce0350381351646ef86b64e6d3840b3869833b.tar.xz
x86/PCI/VMD: Use untracked irq handler
There is no way to know which device in a VMD triggered an interrupt without invoking every registered driver's actions. This uses the untracked irq handler so that a less used device does not trigger spurious interrupt. We have been previously recommending users to enable "noirqdebug", but do not want to force a system setting just to keep this domain functional. Signed-off-by: Keith Busch <keith.busch@intel.com> Acked-by: Bjorn Helgaas <bhelgaas@google.com> Cc: linux-pci@vger.kernel.org Cc: Jon Derrick <jonathan.derrick@intel.com> Link: http://lkml.kernel.org/r/1466200821-29159-2-git-send-email-keith.busch@intel.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'arch/x86/pci')
-rw-r--r--arch/x86/pci/vmd.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/x86/pci/vmd.c b/arch/x86/pci/vmd.c
index 7792aba266df..613cac7395c4 100644
--- a/arch/x86/pci/vmd.c
+++ b/arch/x86/pci/vmd.c
@@ -195,7 +195,7 @@ static int vmd_msi_init(struct irq_domain *domain, struct msi_domain_info *info,
vmdirq->virq = virq;
irq_domain_set_info(domain, virq, vmdirq->irq->vmd_vector, info->chip,
- vmdirq, handle_simple_irq, vmd, NULL);
+ vmdirq, handle_untracked_irq, vmd, NULL);
return 0;
}