2LSs don't always call uthread_runnable
authorBarret Rhoden <brho@cs.berkeley.edu>
Tue, 26 Mar 2013 03:49:04 +0000 (20:49 -0700)
committerBarret Rhoden <brho@cs.berkeley.edu>
Tue, 26 Mar 2013 03:49:04 +0000 (20:49 -0700)
commit971fe069ebe8eba20833c1001ab84a3be53ac4cc
treedb0c6cac3ee842aea6ebeaec64fdd79a3c6963f1
parent1b674d516a8aa0e980b2733387a5ceeaa11a7c45
2LSs don't always call uthread_runnable

More like, they are allowed to call their own sched op, instead of
always calling out to the uthread code.  The uthread wrapper is just
meant for external code that doesn't know the name of the sched op.
This will help with batch wakeup functions.
user/parlib/uthread.c
user/pthread/pthread.c