From: tip-bot for Keith Busch <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: bhelgaas@google.com, jonathan.derrick@intel.com,
keith.busch@intel.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, mingo@kernel.org, hpa@zytor.com
Subject: [tip:irq/core] x86/PCI/VMD: Use untracked irq handler
Date: Sat, 18 Jun 2016 01:07:38 -0700 [thread overview]
Message-ID: <tip-30ce0350381351646ef86b64e6d3840b3869833b@git.kernel.org> (raw)
In-Reply-To: <1466200821-29159-2-git-send-email-keith.busch@intel.com>
Commit-ID: 30ce0350381351646ef86b64e6d3840b3869833b
Gitweb: http://git.kernel.org/tip/30ce0350381351646ef86b64e6d3840b3869833b
Author: Keith Busch <keith.busch@intel.com>
AuthorDate: Fri, 17 Jun 2016 16:00:21 -0600
Committer: Thomas Gleixner <tglx@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.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>
---
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;
}
next prev parent reply other threads:[~2016-06-18 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 22:00 [PATCH 1/2] irq: Add untracked irq handler Keith Busch
2016-06-17 22:00 ` [PATCH 2/2] vmd: use " Keith Busch
2016-06-17 23:00 ` Bjorn Helgaas
2016-06-18 8:07 ` tip-bot for Keith Busch [this message]
2016-06-18 8:07 ` [tip:irq/core] genirq: Add " tip-bot for Keith Busch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tip-30ce0350381351646ef86b64e6d3840b3869833b@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bhelgaas@google.com \
--cc=hpa@zytor.com \
--cc=jonathan.derrick@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.