Lines Matching refs:p_lock
52 * can be performed while holding p_lock, and all sleeping or blocking
53 * operations can be performed without acquiring p_lock.
357 * guarantee exactness, we don't acquire the p_lock of any of the member
361 mutex_enter(&p->p_lock);
364 mutex_exit(&p->p_lock);
405 * p_lock must be held at entry.
883 * The following two routines assume that process's p_lock is held or
891 ASSERT(MUTEX_HELD(&p->p_lock));
934 ASSERT(MUTEX_HELD(&p->p_lock));
1115 mutex_enter(&p->p_lock);
1117 mutex_exit(&p->p_lock);
1121 mutex_enter(&p->p_lock);
1123 mutex_exit(&p->p_lock);
1145 * Suitable for KM_SLEEP allocations. p_lock must not be held at entry.
1756 * b) p_lock will have been acquired earlier in the call path and c) we
1796 * pidlock and p_lock held across exacct_move_mstate().