From: Hollis Blanchard <hollis@austin.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: devel list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: ppc_irq_dispatch_handler and unhandled interrupts
Date: 25 Nov 2002 16:04:29 -0600 [thread overview]
Message-ID: <1038261873.1077.127.camel@granite.austin.ibm.com> (raw)
In-Reply-To: <15838.45984.311938.41129@argo.ozlabs.ibm.com>
On Fri, 2002-11-22 at 16:45, Paul Mackerras wrote:
>
> This is the wrong fix IMO. The situation is no different to calling
> disable_irq during an interrupt handler, and as the comment says, the
> ->end() handler has to deal with that. The problem is that if we
> don't have an ->end() handler we unconditionally call the ->enable()
> handler, which (correctly) just unconditionally enables the
> interrupt.
You're right, not the right fix. I was on a obsolete tree which did not
have a ppc405_uic_end.
But why not require all handlers to have an ->end() handler? If you look
at arch/i386/kernel/irq.c do_IRQ you'll see they just assume there is an
end, simplifying code and removing at least one conditional from the irq
path. In linuxppc-2.5 there are 4 pic drivers entirely without end
handlers: adir_pic, cpc700_pic, gt64260_pic, and ppc403_pic.
-Hollis
--
PowerPC Linux
IBM Linux Technology Center
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-11-25 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 16:58 ppc_irq_dispatch_handler and unhandled interrupts Hollis Blanchard
2002-11-21 18:25 ` Matt Porter
2002-11-22 22:45 ` Paul Mackerras
2002-11-25 22:04 ` Hollis Blanchard [this message]
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=1038261873.1077.127.camel@granite.austin.ibm.com \
--to=hollis@austin.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).