From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>, Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH] genirq: Reenable shared irq debugging in request_*_irq()
Date: Wed, 15 Feb 2017 15:43:54 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1702151542330.3562@nanos> (raw)
Commit 6d83f94db95c ("genirq: Disable the SHIRQ_DEBUG call in
request_threaded_irq for now") disabled the SHIRQ_DEBUG facility for the
irq request side. Unfortunately the 'for now' part and the _FIXME add on to
the CONFIG_SHIRQ_DEBUG guard got forgotten.
It's unfortunately not possible to keep the original idea of just invoking
the newly installed handler due to the reasons described in the commit
which disabled it, but having this debug facility available makes a lot of
sense.
The only way to regain that testing is to invoke the real interrupt
handling mechanism, which will also invoke an already registered handler,
but that's not an issue because _all_ interrupt handlers need to be
prepared for handling spurious interrupts.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
kernel/irq/manage.c | 10 ++--------
1 file changed, 2 insertions(+), 8 deletions(-)
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -1696,23 +1696,17 @@ int request_threaded_irq(unsigned int ir
kfree(action);
}
-#ifdef CONFIG_DEBUG_SHIRQ_FIXME
+#ifdef CONFIG_DEBUG_SHIRQ
if (!retval && (irqflags & IRQF_SHARED)) {
/*
* It's a shared IRQ -- the driver ought to be prepared for it
* to happen immediately, so let's make sure....
- * We disable the irq to make sure that a 'real' IRQ doesn't
- * run in parallel with our fake.
*/
unsigned long flags;
- disable_irq(irq);
local_irq_save(flags);
-
- handler(irq, dev_id);
-
+ generic_handle_irq_desc(desc);
local_irq_restore(flags);
- enable_irq(irq);
}
#endif
return retval;
next reply other threads:[~2017-02-15 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 14:43 Thomas Gleixner [this message]
2017-02-16 14:35 ` [tip:irq/core] " tip-bot for Thomas Gleixner
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=alpine.DEB.2.20.1702151542330.3562@nanos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®