lkml.org 
[lkml]   [2000]   [Oct]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: SA_INTERRUPT
Hi,

On Mon, 2 Oct 2000, Andrea Arcangeli wrote:

> > When that is done, please don't call __sti() directly and use some macro
> > that can be overridden by the architectures.
>
> What do you have in mind while making this suggestion? The irq highlevel layer
> is pretty much architectural indipendent. Just run a diff between the irq.c in
> the IA32 and alpha ports. Also what about the drivers that are just using
> __sti() at the start of the irq handler right now?

m68k uses interrupt levels, so an interrupt with a higher priority can
interrupt another interrupt with a lower priority. To make things more
interesting several m68k machines don't have a seperate external interrupt
controller, so they rely on that the interrupt level isn't lowered during
an interrupt (the ide driver has an ide__sti() because of this).
I can imagine that newer lowend embedded targets have similiar problems
(on the other end I'm just looking at the s390 interrupt code which looks
also interesting).

bye, Roman

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:45    [W:0.038 / U:0.592 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site