> Yep. Any interrupt, actually.
>
> Or the reschedule IPI on SMP systems.
>
> Kernel preemption off an interrupt is actually the most common (and the
> ideal) place to preempt since an interrupt is usually what wakes up a
> task off I/O and sets need_resched. So kernel preemption lets us
> reschedule the higher priority task the moment the interrupt wakes it
> up. Of course, if a lock is held, we have to wait till we drop it.
Thanks for clearing that up, i'll probably need to relook at some of my
code to be sure.
Zwane
-- function.linuxpower.ca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/