Lines Matching full:wake

12  * just woken up (timeout, signal). After the wake up the task has to
62 	.wake		= futex_wake_mark,
116 		 * IN_PROGRESS and a interleaved early wake to WAIT.  in futex_requeue_pi_prepare()
159 	 * wake below: It will assign Q_REQUEUE_PI_IN_PROGRESS and here it will  in futex_requeue_pi_complete()
163 	 * In this case only we skip the wake here and rely on following wake in  in futex_requeue_pi_complete()
164 	 * requeue_pi_wake_futex() to perform the wake if needed.  in futex_requeue_pi_complete()
183 		 * the waiter or to wake it up once the requeue is done.  in futex_requeue_pi_wakeup_sync()
210  * requeue_pi_wake_futex() - Wake a task that acquired the lock during requeue
233  * 6) Wake the waiter task.
275  * Wake the top waiter if we succeed.  If the caller specified set_waiters,
377  * @nr_wake:	number of waiters to wake (must be 1 for requeue_pi)
422 		 * of waiters to wake up via the @nr_wake argument. With  in futex_requeue()
433 		 * waiters. So restrict the number of waiters to wake to  in futex_requeue()
434 		 * one, and only wake it up when the PI futex is  in futex_requeue()
506 			 * Attempt to acquire uaddr2 and wake the top waiter. If we  in futex_requeue()
620 			/* Plain futexes just wake or requeue and are done */  in futex_requeue()
623 					this->wake(&wake_q, this);  in futex_requeue()
765  * uaddr2 which must be PI aware and unique from uaddr.  Normal wakeup will wake