Re: [patch] entry.S calling schedule() with interrupts disabled, 2.2.2

Ingo Molnar (mingo@chiara.csoma.elte.hu)
Mon, 1 Mar 1999 19:22:04 +0100 (CET)

> code, because i think it's buggy. schedule() does not guarantee that the
> 'interrupt state' (IF on UP, the more complex interrupt state on SMP) is
> preserved. In schedule() we do a release_kernel_lock(), which does an
> implicit __sti(). [...]

btw, i'm not only nitpicking, the grand plan is to make it illegal to call
schedule() with interrupts disabled, and remove that __sti() from the
context switch path :) After changing sleep_on* and ret_from_irq i can see
no other places that call schedule() with interrupts disabled.

-- mingo

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