From: Brian Gerst <bgerst@didntduck.org>
To: Swami <swamis@iastate.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Doubt in interrupts
Date: Mon, 02 Jul 2001 14:20:34 -0400 [thread overview]
Message-ID: <3B40BB72.64EE38C6@didntduck.org> (raw)
In-Reply-To: <Pine.OSF.3.95.1010702123304.30601F-100000@isua1.iastate.edu>
Swami wrote:
>
> Hi,
>
> Are there any interrupts which doesn't affect local_irq_count(cpu) or that
> doesn't enter do_IRQ()? (other than NMIs).
>
> Because I'm implementing my own locking routine and I'm getting
> interrupted during spin, but I check and found that in_interupt() returns
> zero.
All hardware interrupts go through do_IRQ. There are also CPU
exceptions and inter-processor interupts (SMP only) that have individual
handlers.
--
Brian Gerst
prev parent reply other threads:[~2001-07-02 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 17:41 Doubt in interrupts Swami
2001-07-02 18:20 ` Brian Gerst [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=3B40BB72.64EE38C6@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swamis@iastate.edu \
/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