src-test2 - FreeBSD source tree

	Commit message (Collapse)	Author	Age	Files	Lines
*	Don't hold the active thread list lock when signaling the gc thread.	Mike Makonnen	2003-05-29	1	-11/+13
\| \| \| \| \| \| \| \| \| \| \| \|	The dead list thread is sufficient for synchronization. Retire the arch_id (ldt array slot) in the gc thread instead of the doing it in the thread itself. Approved by: re/jhb Notes: svn path=/head/; revision=115387
*	Minimize the potential for deadlocks between an exiting thread and it's	Mike Makonnen	2003-05-27	1	-2/+18
\| \| \| \| \| \| \| \| \| \| \|	joiner by making sure all locks and unlocks occur in the same order. For the record the lock order is: DEAD_LIST, THREAD_LIST, exiting thread, joiner thread. Approved by: re/rwatson Notes: svn path=/head/; revision=115357
*	Start locking up the active and dead threads lists. The active threads	Mike Makonnen	2003-05-25	1	-30/+26
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	list is protected by a spinlock_t, but the dead list uses a pthread_mutex because it is necessary to synchronize other threads with the garbage collector thread. Lock/Unlock macros are used so it's easier to make changes to the locks in the future. The 'dead thread list' lock is intended to replace the gc mutex. This doesn't have any practical ramifications. It simply makes it clearer what the purpose of the lock is. The gc will use this lock, instead of the gc mutex, to synchronize access to the dead list with other threads. Modify _pthread_exit() to use these two new locks instead of GIANT_LOCK, and also to properly lock and protect thread state changes, especially with respect to a joining thread. The gc thread was also re-arranged to be more organized and less nested. _pthread_join() was also modified to use the thread list locks. However, locking and unlocking here needs special care because a thread could find itself in a position where it's joining an exiting thread that is waiting on the dead list lock, which this thread (joiner) holds. If the joiner doesn't take care to lock and unlock in the same order they (the joiner and the joinee) could deadlock against each other. Approved by: re/blanket libthr Notes: svn path=/head/; revision=115305
*	Make WARNS2 clean. The fixes mostly included:	Mike Makonnen	2003-05-23	1	-0/+3
\| \| \| \| \| \| \| \| \| \| \|	o removed unused variables o explicit inclusion of header files o prototypes for externally defined functions Approved by: re/blanket libthr Notes: svn path=/head/; revision=115260
*	note to self: do not confuse void* with int.	Mike Makonnen	2003-05-23	1	-1/+1
\| \| \| \| \| \| \|	Approved by: re/blanket libthr Notes: svn path=/head/; revision=115259
*	When a thread exits it does not return from the kernel unless it	Mike Makonnen	2003-05-21	1	-0/+4
\| \| \| \| \| \| \| \| \| \|	is the only remaining thread in the application, in which case we should not core dump, and instead exit gracefully. Approved by: markm/mentor, re/blanket libthr Notes: svn path=/head/; revision=115196
*	- Define curthread as _get_curthread() and remove all direct calls to	Jeff Roberson	2003-04-02	1	-3/+0
\| \| \| \| \| \| \| \| \| \|	_get_curthread(). This is similar to the kernel's curthread. Doing this saves stack overhead and is more convenient to the programmer. - Pass the pointer to the newly created thread to _thread_init(). - Remove _get_curthread_slow(). Notes: svn path=/head/; revision=112965
*	- Add libthr but don't hook it up to the regular build yet. This is an	Jeff Roberson	2003-04-01	1	-0/+186
	adaptation of libc_r for the thr system call interface. This is beta quality code. Notes: svn path=/head/; revision=112918