> Places that call schedule() explicitly holding the BKL are rare enough
> we can probably handle them. I have a patch that does so (thus turning
> all cond_resched() calls into no-ops with the preemptive kernel -- my
> goal). The other implicit situations are near impossible to handle.
There are lots of them hiding 8)
> Summary is, I would love to do things like dismantle the BKLs odd-ball
> features... cleanly and safely. Good luck ;)
You can actually do it with some testing to catch the missed cases. Move
them to spinlocks, lob a check if the lock is held into the schedule code
run it for a while through its various code paths, then remove the debug
once you trust it
-
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 : Mon Jul 15 2002 - 22:00:16 EST