Commit-ID:  30ce0350381351646ef86b64e6d3840b3869833b
Gitweb:     http://git.kernel.org/tip/30ce0350381351646ef86b64e6d3840b3869833b
Author:     Keith Busch <keith.bu...@intel.com>
AuthorDate: Fri, 17 Jun 2016 16:00:21 -0600
Committer:  Thomas Gleixner <t...@linutronix.de>
CommitDate: Sat, 18 Jun 2016 10:00:55 +0200

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.bu...@intel.com>
Acked-by: Bjorn Helgaas <bhelg...@google.com>
Cc: linux-...@vger.kernel.org
Cc: Jon Derrick <jonathan.derr...@intel.com>
Link: 
http://lkml.kernel.org/r/1466200821-29159-2-git-send-email-keith.bu...@intel.com
Signed-off-by: Thomas Gleixner <t...@linutronix.de>

---
 arch/x86/pci/vmd.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/pci/vmd.c b/arch/x86/pci/vmd.c
index 7792aba..613cac7 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;
 }
 

Reply via email to