> We really need a non-signal-based way to tell the scheduler that a task
> can not be scheduled. A lot of the machinery is all there, but private to
> sched.c; the rest is pretty straightforward.
You need interrupts to handle this, even if you don't wrap it in the top
layer of signals it will be able to use much of the code I agree. The nasty
case is the "currently running on another cpu" one. Especially since you
can't just "trap it" - if you IPI that processor it might have moved by the
time the IPI arrives 8)
-
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/
This archive was generated by hypermail 2b29 : Sat Mar 23 2002 - 22:00:25 EST