From: Robert Love <rml@tech9.net>
To: root@chaos.analogic.com
Cc: sanket rathi <sanket@linuxmail.org>, linux-kernel@vger.kernel.org
Subject: Re: interrupt handler
Date: 23 Aug 2002 12:52:20 -0400 [thread overview]
Message-ID: <1030121541.1935.3684.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.3.95.1020823123854.2797A-100000@chaos.analogic.com>
On Fri, 2002-08-23 at 12:45, Richard B. Johnson wrote:
> On 23 Aug 2002, Robert Love wrote:
> > Only the current interrupt handler is disabled... interrupts are
> > normally ON.
>
> No. Check out irq.c, line 446. The interrupts are turned back on
> only if the flag did not have SA_INTERRUPT set. Certainly most
> requests for interrupt services within drivers have SA_INTERRUPT
> set.
Sigh... SA_INTERRUPT is used only for fast interrupts. Certainly most
drivers do not have it (and most that do are probably from the way old
days when we went through great pains to distinguish between fast and
slow interrupt handlers).
Today, very few things should run with all interrupts disabled. That is
just dumb. In fact, on this system, it seems only the timer interrupt
sets SA_INTERRUPT...
Robert Love
next prev parent reply other threads:[~2002-08-23 16:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 11:58 interrupt handler sanket rathi
2002-08-23 12:17 ` Richard B. Johnson
2002-08-23 16:17 ` Robert Love
2002-08-23 16:45 ` Richard B. Johnson
2002-08-23 16:52 ` Robert Love [this message]
2002-08-23 20:45 ` george anzinger
-- strict thread matches above, loose matches on Subject: below --
2004-04-15 10:02 Interrupt handler MNH
2004-04-17 18:57 ` Karim Yaghmour
2002-08-23 6:22 interrupt handler Kerenyi Gabor
2002-08-23 5:45 Kerenyi Gabor
2002-08-23 13:07 ` Richard B. Johnson
2002-08-23 4:58 Kerenyi Gabor
2002-08-21 14:25 Interrupt Handler sanket rathi
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=1030121541.1935.3684.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=sanket@linuxmail.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