src-test2/lib/libthr/thread, branch release/5.2.1_cvs FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F5.2.1_cvs 2004-02-23T15:32:56Z This commit was manufactured by cvs2svn to create tag 2004-02-23T15:32:56Z cvs2svn cvs2svn@FreeBSD.org 2004-02-23T15:32:56Z urn:sha1:84a7b99b4e02a260bf7ff9b540032f4cb7bc612a 'RELENG_5_2_1_RELEASE'. This commit was manufactured to restore the state of the 5.2.1-RELEASE image. Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs. When _PTHREADSINVARIANTS is defined SIGABRT is not included 2003-07-08T09:58:23Z Mike Makonnen mtm@FreeBSD.org 2003-07-08T09:58:23Z urn:sha1:393441d43b6de1b136dc816902477f8e34ff90a8 in the set of signals to block. Also, make the PANIC macro call abort() instead of simply exiting. Change all instances of THR_LOCK/UNLOCK, etc to UMTX_*. 2003-07-06T10:18:48Z Mike Makonnen mtm@FreeBSD.org 2003-07-06T10:18:48Z urn:sha1:659045ffbfab93ae8438b07e81c09da1271bd9d8 It is a more acurate description of the locks they operate on. There's no need for _umtxtrylock to be a separate function. 2003-07-06T10:10:32Z Mike Makonnen mtm@FreeBSD.org 2003-07-06T10:10:32Z urn:sha1:964407197732fe475fe8f9a54cb68884dd447a94 Roll it into the pre-existing macro that's used to call it. _pthread_mutex_trylock() is another internal libc function that must block 2003-07-03T13:28:53Z Mike Makonnen mtm@FreeBSD.org 2003-07-03T13:28:53Z urn:sha1:e921a3c976e6f2841902088af2af85448881ce48 signals. Begin making libthr async signal safe. 2003-07-02T02:05:23Z Mike Makonnen mtm@FreeBSD.org 2003-07-02T02:05:23Z urn:sha1:f493d09ae7e2d3588750371083fd7b06beb6e2b8 Create a private, single underscore, version of pthread_mutex_unlock for libc. pthread_mutex_lock already has one. These versions are different from the ones that applications will link against because they block all signals from the time a call to lock the mutex is made until it is successfully unlocked. Do not attempt to reque a thread on a mutex queue. It may be that 2003-07-01T15:52:09Z Mike Makonnen mtm@FreeBSD.org 2003-07-01T15:52:09Z urn:sha1:745a4a9ef8ee3864c88b94a771d30d9475641fc9 a thread receives a spurious wakeup from sigtimedwait(), so make sure that the call to the queueing code is called only once before entering the loop (not in the loop). This should fix some fatal errors people are seeing with messages stating the thread is already on the mutex queue. These errors may still be triggered from signal handlers; however, since that part of the code is not locked down yet. Catchup with _thread_suspend() changes. 2003-06-30T12:35:31Z Mike Makonnen mtm@FreeBSD.org 2003-06-30T12:35:31Z urn:sha1:fadd82e36791b989a9636e15c2c81c716277183a Sweep through pthread locking and use the new locking primitives for 2003-06-29T23:51:04Z Mike Makonnen mtm@FreeBSD.org 2003-06-29T23:51:04Z urn:sha1:dbc6f4c07d5f2ea73bb7f1845acccd55049a60dd libthr. Locking primitives and operations in libthr should use struct umtx, 2003-06-29T23:49:41Z Mike Makonnen mtm@FreeBSD.org 2003-06-29T23:49:41Z urn:sha1:2234d5bea27e14811726a905f5a933389335055c not spinlock_t. Spinlock_t and the associated functions and macros may require blocking signals in order for async-safe libc functions to behave appropriately in libthr. This is undesriable for libthr internal locking. So, this is the first step in completely separating libthr from libc's locking primitives. Three new macros should be used for internal libthr locking from now on: THR_LOCK, THR_TRYLOCK, THR_UNLOCK.