From: Jeff Garzik <jeff@garzik.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [proposed patch] via-rhine: prevent oops when requesting an IRQ
Date: Thu, 06 Nov 2008 01:07:41 -0500 [thread overview]
Message-ID: <491289AD.9070401@garzik.org> (raw)
In-Reply-To: <20081104192357.2b0dbe22@redhat.com>
Chuck Ebbert wrote:
> via-rhine: prevent oops when requesting an IRQ
>
> via-rhine requests an IRQ before it's ready to handle an interrupt.
> It oopses when CONFIG_DEBUG_SHIRQ is enabled.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=469303
>
> ---
>
> NOTE: UNTESTED: Is it okay to init the hardware before requesting the
> IRQ, or should that be done afterward?
First of all, _ideally_ your interrupt handler should be able to any
state of software initialization, once registers are mapped. So I would
first concentrate on "hardening" the interrupt handler, if feasible.
It is certainly a common technique to disable interrupts somehow, during
initialization of the hardware. Note, though, that doing things before
request_irq() is no real guarantee you are out of danger -- you might be
on a shared PCI irq, and your init causes that interrupt to "scream"
even though your driver has not registered the irq.
Jeff
next prev parent reply other threads:[~2008-11-06 6:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 0:23 [proposed patch] via-rhine: prevent oops when requesting an IRQ Chuck Ebbert
2008-11-06 6:07 ` Jeff Garzik [this message]
2008-11-10 22:28 ` Chuck Ebbert
2008-11-10 22:35 ` Jeff Garzik
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=491289AD.9070401@garzik.org \
--to=jeff@garzik.org \
--cc=cebbert@redhat.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).