summaryrefslogtreecommitdiffstats
path: root/lib/libthr/thread/thr_create.c
Commit message (Collapse)AuthorAgeFilesLines
* Fix known issues which blow up the process after dlopen("libthr.so")kib2015-01-181-2/+6
| | | | | | | | | | | | | | | | | | | | | (or loading a dso linked to libthr.so into process which was not linked against threading library). MFC r276630: Remove interposing, fix malloc, reinstall signal handlers wrappers on libthr load. MFC r276681: Avoid calling internal libc function through PLT or accessing data though GOT. MFC r277032: Reduce the size of the interposing table and amount of cancellation-handling code in the libthr. MFC note: r276646 ("do not erronously export 'openat' symbol from rtld") is not applicable to stable/10 yet, since PATHFDS support was not merged.
* Implement the __pthread_map_stacks_exec() for libthr.kib2011-01-091-0/+11
| | | | | | | | | | | | Stack creation code is changed to call _rtld_get_stack_prot() to get the stack protection right. There is a race where thread is created during dlopen() of dso that requires executable stacks. Then, _rtld_get_stack_prot() may return PROT_READ | PROT_WRITE, but thread is still not linked into the thread list. In this case, the callback misses the thread stack, and rechecks the required protection afterward. Reviewed by: davidxu
* add code to support stack unwinding when thread exits. note that onlydavidxu2010-09-151-0/+5
| | | | | | defer-mode cancellation works, asynchrnous mode does not work because it lacks of libuwind's support. stack unwinding is not enabled unless LIBTHR_UNWIND_STACK is defined in Makefile.
* Convert thread list lock from mutex to rwlock.davidxu2010-09-131-16/+9
|
* Add signal handler wrapper, the reason to add it becauses there aredavidxu2010-09-011-13/+0
| | | | | | | | | | | | | | | | | | | | | | | some cases we want to improve: 1) if a thread signal got a signal while in cancellation point, it is possible the TDP_WAKEUP may be eaten by signal handler if the handler called some interruptibly system calls. 2) In signal handler, we want to disable cancellation. 3) When thread holding some low level locks, it is better to disable signal, those code need not to worry reentrancy, sigprocmask system call is avoided because it is a bit expensive. The signal handler wrapper works in this way: 1) libthr installs its signal handler if user code invokes sigaction to install its handler, the user handler is recorded in internal array. 2) when a signal is delivered, libthr's signal handler is invoke, libthr checks if thread holds some low level lock or is in critical region, if it is true, the signal is buffered, and all signals are masked, once the thread leaves critical region, correct signal mask is restored and buffered signal is processed. 3) before user signal handler is invoked, cancellation is temporarily disabled, after user signal handler is returned, cancellation state is restored, and pending cancellation is rescheduled.
* Use UMTX_OP_WAIT_UINT_PRIVATE and UMTX_OP_WAKE_PRIVATE to savedavidxu2008-04-291-1/+1
| | | | time in kernel(avoid VM lookup).
* Avoid various shadowed variables. libthr is now almost WARNS=4 clean exceptdelphij2008-04-231-5/+5
| | | | | | for some const dequalifiers that needs more careful investigation. Ok'ed by: davidxu
* don't reduce new thread's refcount if current thread can not set cpusetdavidxu2008-03-191-1/+1
| | | | for it, since the new thread will reduce it by itself.
* - Trim trailing spaces.davidxu2008-03-191-8/+8
| | | | - Use a different sigmask variable name to avoid confusing.
* - Copy signal mask out before THR_UNLOCK(), because THR_UNLOCK() may calldavidxu2008-03-181-4/+10
| | | | | | | | _thr_suspend_check() which messes sigmask saved in thread structure. - Don't suspend a thread has force_exit set. - In pthread_exit(), if there is a suspension flag set, wake up waiting- thread after setting PS_DEAD, this causes waiting-thread to break loop in suspend_common().
* Actually delete SIGCANCEL mask for suspended thread, so the signal will notdavidxu2008-03-161-3/+2
| | | | be masked when it is resumed.
* Restore code setting new thread's scheduler parameters, I was thinkingdavidxu2008-03-061-15/+11
| | | | | | that there might be starvations, but because we have already locked the thread, the cpuset settings will always be done before the new thread does real-world work.
* Use cpuset defined in pthread_attr for newly created thread, for now,davidxu2008-03-051-20/+51
| | | | | | | we set scheduling parameters and cpu binding fully in userland, and because default scheduling policy is SCHED_RR (time-sharing), we set default sched_inherit to PTHREAD_SCHED_INHERIT, this saves a system call.
* If a new thread is created, it inherits current thread's signal masks,davidxu2008-03-041-1/+16
| | | | | | | | however if current thread is executing cancellation handler, signal SIGCANCEL may have already been blocked, this is unexpected, unblock the signal in new thread if this happens. MFC after: 1 week
* implement pthread_attr_getaffinity_np and pthread_attr_setaffinity_np.davidxu2008-03-041-1/+5
|
* - Remove variable _thr_scope_system, all threads are system scope.davidxu2006-12-151-5/+0
| | | | | - Rename _thr_smp_cpus to boolean variable _thr_is_smp. - Define CPU_SPINWAIT macro for each arch, only X86 supports it.
* Eliminate atomic operations in thread cancellation functions, it shoulddavidxu2006-11-241-2/+2
| | | | reduce overheads of cancellation points.
* use rtprio_thread system call to get or set thread priority.davidxu2006-09-211-6/+8
|
* Use umutex APIs to implement pthread_mutex, member pp_mutexq is addeddavidxu2006-08-281-0/+1
| | | | | | into pthread structure to keep track of locked PTHREAD_PRIO_PROTECT mutex, no real mutex code is changed, the mutex locking and unlocking code should has same performance as before.
* Caching scheduling policy and priority in userland, a critical but baddlydavidxu2006-07-131-4/+3
| | | | | written application is frequently changing thread priority for SCHED_OTHER policy.
* Use thr_setscheduler, thr_getscheduler and thr_setschedparam to implementdavidxu2006-07-131-2/+3
| | | | pthread functions.
* Use kernel facilities to support real-time scheduling.davidxu2006-07-121-25/+17
|
* WARNS level 4 cleanup.davidxu2006-04-041-1/+3
|
* Remove priority mutex code because it does not work correctly,davidxu2006-03-271-1/+0
| | | | | | | | | to make it work, turnstile like mechanism to support priority propagating and other realtime scheduling options in kernel should be available to userland mutex, for the moment, I just want to make libthr be simple and efficient thread library. Discussed with: deischen, julian
* Fix a bug recently introduced, the _thread_active_count should bedavidxu2006-01-081-0/+1
| | | | decreased if thread can not be created.
* Refine thread suspension code, now thread suspension is a blockabledavidxu2006-01-051-29/+53
| | | | | | | operation, the caller is blocked util target threads are really suspended, also avoid suspending a thread when it is holding a critical lock. Fix a bug in _thr_ref_delete which tests a never set flag.
* Update copyright.davidxu2005-12-171-19/+13
|
* The pthread_attr_set_createsuspend_np was broken, fix it bydavidxu2005-10-101-1/+1
| | | | replacing THR_FLAGS_SUSPENDED with THR_FLAGS_NEED_SUSPEND.
* Include needed headers that were obtained through <pthread.h>. Sort headersstefanf2005-09-011-1/+2
| | | | while here.
* Use thr_new syscall to create a new thread, obscure context operationsdavidxu2005-04-231-24/+16
| | | | is no longer needed.
* Add debugger event reporting support, current only TD_CREATE and TD_DEATHdavidxu2005-04-121-3/+18
| | | | events are reported.
* Import my recent 1:1 threading working. some features improved includes:davidxu2005-04-021-96/+131
| | | | | | | | | | | | | | | | 1. fast simple type mutex. 2. __thread tls works. 3. asynchronous cancellation works ( using signal ). 4. thread synchronization is fully based on umtx, mainly, condition variable and other synchronization objects were rewritten by using umtx directly. those objects can be shared between processes via shared memory, it has to change ABI which does not happen yet. 5. default stack size is increased to 1M on 32 bits platform, 2M for 64 bits platform. As the result, some mysql super-smack benchmarks show performance is improved massivly. Okayed by: jeff, mtm, rwatson, scottl
* Adjust code to support AMD64, on AMD64, thread needs to set fsbase bydavidxu2004-08-191-3/+20
| | | | | itself before it can execute any other code, so new thread should be created with all signals are masked until after fsbase is set.
* Record the offset of thr_id in the thread structure. Required formarcel2004-07-041-0/+1
| | | | debugging.
* Change the thread ID (thr_id_t) used for 1:1 threading from being amarcel2004-07-021-9/+0
| | | | | | | | | | | | | | | | | | | | pointer to the corresponding struct thread to the thread ID (lwpid_t) assigned to that thread. The primary reason for this change is that libthr now internally uses the same ID as the debugger and the kernel when referencing to a kernel thread. This allows us to implement the support for debugging without additional translations and/or mappings. To preserve the ABI, the 1:1 threading syscalls, including the umtx locking API have not been changed to work on a lwpid_t. Instead the 1:1 threading syscalls operate on long and the umtx locking API has not been changed except for the contested bit. Previously this was the least significant bit. Now it's the most significant bit. Since the contested bit should not be tested by userland, this change is not expected to be visible. Just to be sure, UMTX_CONTESTED has been removed from <sys/umtx.h>. Reviewed by: mtm@ ABI preservation tested on: i386, ia64
* When a thread is created suspended have libthr suspend it explicitlymtm2004-06-301-10/+3
| | | | instead of asking the kernel to do it when we create the thread.
* Make libthr async-signal-safe without costly signal masking. The guidlines Imtm2004-05-201-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | followed are: Only 3 functions (pthread_cancel, pthread_setcancelstate, pthread_setcanceltype) are required to be async-signal-safe by POSIX. None of the rest of the pthread api is required to be async-signal-safe. This means that only the three mentioned functions are safe to use from inside signal handlers. However, there are certain system/libc calls that are cancellation points that a caller may call from within a signal handler, and since they are cancellation points calls have to be made into libthr to test for cancellation and exit the thread if necessary. So, the cancellation test and thread exit code paths must be async-signal-safe as well. A summary of the changes follows: o Almost all of the code paths that masked signals, as well as locking the pthread structure now lock only the pthread structure. o Signals are masked (and left that way) as soon as a thread enters pthread_exit(). o The active and dead threads locks now explicitly require that signals are masked. o Access to the isdead field of the pthread structure is protected by both the active and dead list locks for writing. Either one is sufficient for reading. o The thread state and type fields have been combined into one three-state switch to make it easier to read without requiring a lock. It doesn't need a lock for writing (and therefore for reading either) because only the current thread can write to it and it is an integer value. o The thread state field of the pthread structure has been eliminated. It was an unnecessary field that mostly duplicated the flags field, but required additional locking that would make a lot more code paths require signal masking. Any truly unique values (such as PS_DEAD) have been reborn as separate members of the pthread structure. o Since the mutex and condvar pthread functions are not async-signal-safe there is no need to muck about with the wait queues when handling a signal ... o ... which also removes the need for wrapping signal handlers and sigaction(2). o The condvar and mutex async-cancellation code had to be revised as a result of some of these changes, which resulted in semi-unrelated changes which would have been difficult to work on as a separate commit, so they are included as well. The only part of the changes I am worried about is related to locking for the pthread joining fields. But, I will take a closer look at them once this mega-patch is committed.
* Remove the garbage collector thread. All resources are freedmtm2004-03-281-15/+0
| | | | | in-line. If the exiting thread cannot release a resource, then the next thread to exit will release it.
* Move the initialization of thread priority to a common function.mtm2004-02-181-1/+0
|
* Preparations to make libthr work in multi-threaded fork()ing applications.mtm2003-12-261-24/+1
| | | | | | | | | | | | | o Remove some code duplication between _thread_init(), which is run once to initialize libthr and the intitial thread, and pthread_create(), which initializes newly created threads, into a new function called from both places: init_td_common() o Move initialization of certain parts of libthr into a separate function. These include: - Active threads list and it's lock - Dead threads list and it's lock & condition variable - Naming and insertion of the initial thread into the active threads list.
* When creating a pthread in the suspended state their were twomtm2003-12-151-2/+4
| | | | | | | | problems: (1) The wrong flag was being checked for in the attribute (2) The pthread's state was not being set to indicate it was suspended. Noticed by: Igor Sysoev <is@rambler-co.ru>
* It's unnecessary to lock the thread during creation. Simply extendmtm2003-05-291-5/+2
| | | | | | the scope of the active thread list lock. Approved by: re/jhb
* Decouple the thread stack [de]allocating functions from the 'dead threads list'mtm2003-05-261-3/+2
| | | | | | | lock. It's not really necessary and we don't need the added complexity or potential for deadlocks. Approved by: re/blanket libthr
* Return gracefully, rather than aborting, when the maximum concurrentmtm2003-05-251-1/+12
| | | | | | threads per process has been reached. Return EAGAIN, as per spec. Approved by: re/blanket libthr
* Part of the last patch.mtm2003-05-251-7/+7
| | | | | | | Modify the thread creation and thread searching routine to lock the thread lists with the new locks instead of GIANT_LOCK. Approved by: re/blanket libthr
* Make WARNS2 clean. The fixes mostly included:mtm2003-05-231-1/+0
| | | | | | | | o removed unused variables o explicit inclusion of header files o prototypes for externally defined functions Approved by: re/blanket libthr
* Re-enable the garbage collector thread in anticipation of furthermtm2003-05-211-2/+0
| | | | | | | locking work. I can't see anything obviously wrong with it (other than the need to update the locking). Approved by: markm/mentor, re/blanket libthr
* Fix build breakage (on ia64) caused by a missing file descriptor tomarcel2003-04-201-1/+1
| | | | _thread_printf(). Use STDERR_FILENO as the file descriptor.
* - Pass a ucontext_t to _set_curthread. If non-NULL the new thread is setjake2003-04-031-4/+4
| | | | | | | | as curthread in the new context, so that it will be set automatically when the thread is switched to. This fixes a race where we'd run for a little while with curthread unset in _thread_start. Reviewed by: jeff
* - Define curthread as _get_curthread() and remove all direct calls tojeff2003-04-021-12/+4
| | | | | | | _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().
OpenPOWER on IntegriCloud