From: Robert Love <rml@tech9.net>
To: Jeremy Hall <jhall@maoz.com>
Cc: linux-mm@kvack.org
Subject: Re: interrupt context
Date: 14 Apr 2003 14:56:50 -0400 [thread overview]
Message-ID: <1050346609.3664.55.camel@localhost> (raw)
In-Reply-To: <200304141851.h3EIpZjV015008@sith.maoz.com>
On Mon, 2003-04-14 at 14:51, Jeremy Hall wrote:
> On a UP machine, is it possible for two interrupts to occur at once? as
> in, can card a create an interrupt while card b is in interrupt context?
Yes. Normally, all interrupts are enabled (the interrupt system is on)
but the _current_ interrupt line is masked out. Thus you will never get
a recursive interrupt (A while processing A) but you may get A while
processing B.
Note if SA_INTERRUPT flag was given to request_irq() then the interrupt
is a "fast" interrupt and runs with all interrupts disabled on the local
processor.
> what about an SMP machine operating in UP mode (nosmp)
By nature of above, yes.
If you need to ensure concurrency is protected in your interrupt
handler, grab a lock and disable interrupts around the critical region.
Robert Love
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-04-14 18:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 18:51 Jeremy Hall
2003-04-14 18:56 ` Robert Love [this message]
2003-04-14 19:32 ` Jeremy Hall
2003-04-14 19:35 ` Robert Love
2003-04-14 21:09 ` Jeremy Hall
2003-04-14 21:18 ` Robert Love
2003-04-14 21:48 ` Jeremy Hall
2003-04-14 22:57 ` Robert Love
2003-04-15 3:44 ` Jeremy Hall
2003-04-15 4:14 ` Jeremy Hall
2003-04-15 21:40 ` Robert Love
2003-04-15 23:02 ` Jeremy Hall
2003-04-16 3:41 ` Jeremy Hall
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=1050346609.3664.55.camel@localhost \
--to=rml@tech9.net \
--cc=jhall@maoz.com \
--cc=linux-mm@kvack.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