uthread creation is now init, slims 2ls sched_ops
authorBarret Rhoden <brho@cs.berkeley.edu>
Mon, 22 Aug 2011 23:28:30 +0000 (16:28 -0700)
committerKevin Klues <klueska@cs.berkeley.edu>
Thu, 3 Nov 2011 00:36:06 +0000 (17:36 -0700)
commit24601dc6983754c667c87f5afc11d78b6b91b507
tree5f39922a7b7c976e55b5f52089baad0d684bb5c0
parent6a855fec5c382a9263c95a405b635189e7e46bf3
uthread creation is now init, slims 2ls sched_ops

2LSs now create their threads however they want, and then call
uthread_init() on them.  Later, they must call uthread_cleanup().

Thread creation/destruction is more 'top-down' this way, and the 2LS
must be sure to call uthread_lib_init() in its initialization routines,
and call uthread_cleanup() when it is done with a uthread.

With great power comes great responsibility.
tests/mhello.c
tests/syscall.c
user/parlib/include/uthread.h
user/parlib/uthread.c
user/pthread/pthread.c