README revision 1.3
1 This pthread package is/will be based on the POSIX1003.4a Draft 7 pthread 2 standard, and Frank Mullers paper on signal handelling presented 3 at the Winter 93 USENIX conference. 4 5 It is currently being designed and written by me, Chris Provenzano. 6 All bug, comments, and questions can be sent me at either 7 proven (a] athena.mit.edu or proven (a] sun-lamp.cs.berkeley.edu 8 PLEASE, don't send questions, bugs or patches to any of the *BSD* mailing lists. 9 10 Thanks goes to John Carr jfc (a] mit.edu for porting this to the IBM/RT, 11 and for his bug reports and fixes, Greg Hudson and Mark Eichin for the 12 testing they've done, and all the others. 13 14 PORTING 15 One of the goals of this user space implementation of pthreads is that it 16 be portable. I have minimized the ammount of assembler code necessary, 17 but some is. 18 19 If you want to port it to another platform here are a few basic hints. 20 21 There are currently three files you'll have to creat for your 22 architecture, machdep.h, machdep.c and syscall.S. 23 The first two are necessary to get the context switch section of 24 the pthread package running, the third is for all the syscalls. 25 26 To do an initial port, create an appropriate machdep.h, and machdep.c 27 and define PTHREAD_INITIAL_PORT in the Makefile 28 29 Comment out references to the stdio package. 30 31 INCLUDE FILES AND PORTING 32 To continue to make this package portable, some basic rules on includes 33 files must be followed. 34 35 pthread.h should be included first (if it is to be included). 36 machdep.h should define size_t if the system doesn't define it already 37 38 posix.h should be included last. This file is used to correct non 39 POSIX features, after everything else has been defined. 40 41 INTERNAL LOCKING 42 To prevent deadlocks the following rules were used for locks. 43 44 1. Local locks for mutex queues and other like things are only locked 45 by running threads, at NO time will a local lock be held by 46 a thread in a non running state. 47 2. Only threads that are in a run state can attempt to lock another thread, 48 this way, we can assume that the lock will be released shortly, and don't 49 have to unlock the local lock. 50 3. The only time a thread will have a pthread->lock and is not in a run 51 state is when it is in the reschedule routine. 52 4. The reschedule routine assumes all local locks have been released, 53 there is a lock on the currently running thread (pthread_run), 54 and that this thread is being rescheduled to a non running state. 55 It is safe to unlock the currently running threads lock after it 56 has been rescheduled. 57 5. The reschedule routine locks the kernel, sets the state of the currently 58 running thread, unlocks the currently running thread, calls the 59 context switch routines. 60 6 the kernel lock is used only ... 61 62 63 7. The order of locking is ... 64 65 1 local locks 66 2 pthread->lock /* Assumes it will get it soon */ 67 3 pthread_run->lock /* Assumes it will get it soon, but must release 2 */ 68 4 kernel lock /* Currently assumes it will ALWAYS get it. */ 69 70 8. The kernel lock will be changed to a spin lock for systems that 71 already support kernel threads, this way we can mutiplex threads onto 72 kernel threads. 73 9. There are points where the kernel is locked and it needs to get 74 either a local lock or a pthread lock, if at these points the code 75 fails to get the lock the kernel gives up and sets a flag which will 76 be checked at a later point. 77 10. Interrupts are dissabled while the kernel is locked, the interrupt 78 mask must be checked afterwards or cleared in some way, after interrputs 79 have been reenabled, this allows back to back interrupts, but should always 80 avoid missing one. 81 82 Copyright (c) 1993 Chris Provenzano. All rights reserved. 83 84 This product includes software developed by the Univeristy of California, 85 Berkeley and its contributors. 86
Indexes created Sun Nov 02 07:10:05 GMT 2025