From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@osdl.org>,
arjan@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [patch, -rc5-mm3] fix irqpoll some more
Date: Tue, 06 Jun 2006 09:25:55 -0400 [thread overview]
Message-ID: <1149600355.16247.49.camel@localhost.localdomain> (raw)
In-Reply-To: <20060605084938.GA31915@elte.hu>
On Mon, 2006-06-05 at 10:49 +0200, Ingo Molnar wrote:
> + /*
> + * HACK:
> + *
> + * In the first pass we dont touch handlers that are behind
> + * a disabled IRQ line. In the second pass (having no other
> + * choice) we ignore the disabled state of IRQ lines. We've
> + * got a screaming interrupt, so we have the choice between
> + * a real lockup happening due to that screaming interrupt,
> + * against a theoretical locking that becomes possible if we
> + * ignore a disabled IRQ line.
FYI, with irqpoll on in my i386 SMP machine, I hit this theoretical
locking every time in the vortex driver.
-- Steve
> + *
> + * FIXME: proper disable_irq_handler() API would remove the
> + * need for this hack.
> + */
> + if (!ok && first_pass) {
> + first_pass = 0;
> + goto repeat;
> + }
> +
> /* So the caller can adjust the irq error counts */
> return ok;
> }
next prev parent reply other threads:[~2006-06-06 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200606050600.k5560GdU002338@shell0.pdx.osdl.net>
[not found] ` <1149497459.23209.39.camel@localhost.localdomain>
2006-06-05 8:49 ` [patch, -rc5-mm3] fix irqpoll some more Ingo Molnar
2006-06-05 13:05 ` Alan Cox
2006-06-05 12:52 ` Ingo Molnar
2006-06-06 13:25 ` Steven Rostedt [this message]
2006-06-06 13:53 ` Ingo Molnar
2006-06-06 14:40 ` Steven Rostedt
2006-06-06 14:59 ` Ingo Molnar
2006-06-06 15:32 ` Steven Rostedt
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=1149600355.16247.49.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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