Lines Matching full:semaphore
2539 /* For each semaphore, we maintain a stack of SOs. When a 'post'
2540 operation is done on a semaphore (unlocking, essentially), a new SO
2543 SO), and the SO is pushed on the semaphore's stack.
2546 semaphore, we pop a SO off the semaphore's stack (which should be
2548 dependencies between posters and waiters of the semaphore.
2552 happened for the semaphore.
2554 Imagine T1 and T2 both post once on a semaphore S, and T3 waits
2559 When a semaphore is initialised with value N, we do as if we'd
2560 posted N times on the semaphore: basically create N SOs and do a
2562 semaphore to acquire a dependency on the initialisation point,
2565 We don't emit an error for DESTROY_PRE on a semaphore we don't know
2604 /* xa is the stack for this semaphore. */
2616 /* hmm, that's odd. No stack for this semaphore. */
2632 /* Empty out the semaphore's SO stack. This way of doing it is
2662 /* Empty out the semaphore's SO stack. This way of doing it is
2724 the 'sem' from this semaphore's SO-stack, and do a strong recv
2726 for the semaphore. */
2755 " semaphore without prior sem_post");
