Lines Matching defs:up
95 static kthread_t *lwpsobj_pi_owner(upimutex_t *up);
526 lwpsobj_pi_owner(upimutex_t *up)
528 return (up->upi_owner);
656 * Unlocks upimutex, waking up waiters if any. upimutex kmem is freed if
827 * This is the key to preventing a missed wake-up. Otherwise, the
852 * If we wake up due to an interrupt or timeout, we may
896 * could be due to a spurious wake-up or a NOTRECOVERABLE
903 * If the thread wakes up from turnstile_block with the lock
923 * Wake-up without the upimutex held. Either this is a
924 * spurious wake-up (due to signals, forkall(), whatever), or
939 * same time as curthread having been woken up
951 * set to LOCK_NOTRECOVERABLE, and the wake-up of
1113 * woken up. Since user object is unmapped, it could
1115 * The waiters will now all wake up and return
1298 * for me but I have woken up due to a signal or
1518 * Always wake up an lwp (if any) waiting on lwpchan. The woken lwp will
1529 * was woken up by a signal. This time, the waiter recomputes
1618 * set up another on_fault() for a possible fault
2293 /* Wake the new lock holder(s) up. */
2378 * Set up another on_fault() for a possible fault
2810 * Wake up a thread asleep on a user-level synchronization
2857 * Clean up a left-over process-shared robust mutex
2919 * If there are waiters, we wake up one or all of them.
2920 * It doesn't hurt to wake them up in error since
3167 * Always wake up an lwp (if any) waiting on lwpchan. The woken lwp will
3178 * was woken up by a signal. This time, the waiter recomputes