From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: test for "spurious" IRQ ignores possible IRQ_WAKE_THREAD value
Date: Thu, 17 Sep 2009 16:08:32 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0909171605320.5014@localhost> (raw)
In-Reply-To: <20090917193416.GE8817@lenovo>
On Thu, 17 Sep 2009, Cyrill Gorcunov wrote:
> [Robert P. J. Day - Mon, Sep 14, 2009 at 04:34:48PM -0400]
> | On Mon, 14 Sep 2009, Robert P. J. Day wrote:
> |
> | > never ashamed to embarrass myself in public, i just noticed the
> | > following. from kernel/irq/spurious.c:
> | >
> | > ...
> | > static void
> | > __report_bad_irq(unsigned int irq, struct irq_desc *desc,
> | > irqreturn_t action_ret)
> | > {
> | > struct irqaction *action;
> | >
> | > if (action_ret != IRQ_HANDLED && action_ret != IRQ_NONE) {
> | > printk(KERN_ERR "irq event %d: bogus return value %x\n",
> | > irq, action_ret);
> | >
> | > but from include/linux/irqreturn.h, we see *three* possible return
> | > values:
> | >
> | > enum irqreturn {
> | > IRQ_NONE,
> | > IRQ_HANDLED,
> | > IRQ_WAKE_THREAD,
> | > };
> | >
> | > typedef enum irqreturn irqreturn_t;
> | > #define IRQ_RETVAL(x) ((x) != IRQ_NONE)
> | >
> | > is there an inconsistency here?
> |
> ...
>
> Hi Robert,
>
> It could that IRQ_WAKE_THREAD is just missed here. I suppose it was
> brough there as thread irq merged. But I think only Thomas know for
> sure, I definitely miss something :) CC'ed
actually, after a bit more reading, i found this in
kernel/irq/handle.c:
...
switch (ret) {
case IRQ_WAKE_THREAD:
/*
* Set result to handled so the spurious check
* does not trigger.
*/
ret = IRQ_HANDLED;
...
so it looks like that value of IRQ_WAKE_THREAD is simply "mapped" to
IRQ_HANDLED, and perhaps that's done before __report_bad_irq is ever
called so that that latter routine never sees a value of
IRQ_WAKE_THREAD. but that's just a guess.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2009-09-17 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 20:30 test for "spurious" IRQ ignores possible IRQ_WAKE_THREAD value Robert P. J. Day
2009-09-14 20:34 ` Robert P. J. Day
2009-09-17 19:34 ` Cyrill Gorcunov
2009-09-17 19:52 ` Thomas Gleixner
2009-09-17 20:08 ` Robert P. J. Day [this message]
2009-09-17 20:18 ` Cyrill Gorcunov
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.LFD.2.00.0909171605320.5014@localhost \
--to=rpjday@crashcourse.ca \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.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.