Re: intel x86 instruction "cli"

From: Kasper Dupont (kasperd_at_daimi.au.dk)
Date: 03/19/04 

Date: Fri, 19 Mar 2004 15:41:50 +0100

news wrote:
>
> But if ints are enabled, lower priority interrupts could be
> triggered too, right?

That depends on exactly how the PIC works (which I
unfortunately don't know). Of course you could
implement priorities in software by telling the PIC
to modify the mask appropriately.

Higher levels have some control over what is going
on. For example the IDE layer can actually decide if
an interrupt for a given unit may be interrupted.
(hdparm -u) 

-- 
Kasper Dupont -- der bruger for meget tid paa usenet.
For sending spam use mailto:aaarep@daimi.au.dk
/* Would you like fries with that? */

Relevant Pages

  • Re: submit_bh leaves interrupts on upon return
    ... but why does it need to leave interrupts on if the calling ... >>state was with ints off. ... so I altered the calling sequence to call with ints on. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • submit_bh leaves interrupts on upon return
    ... Any reason why submit_bh should turn on interrupts after being called by ... elevatoring, but why does it need to leave interrupts on if the calling ... state was with ints off. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: [PATCH] dynamic tick patch
    ... >> Good news is that it does seem to reduce number of interrupts. ... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: Interrupt Question
    ... > Disabling interrupts can not fix the problem only reduce the occurrence ... > A high priority interrupt which depends on data generated in a low priority ... ISR1 just by not enabling INTs in the routine. ...
    (comp.arch.embedded)
  • Re: submit_bh leaves interrupts on upon return
    ... > Any reason why submit_bh should turn on interrupts after being called by ... > state was with ints off. ... doesn't save interrupt state, so you will always leave with interrupts ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)