Lines Matching refs:we

9 	ps_spinlock.  C is always preceded by B, since we can't reach it
10 	other than through B and we don't drop ps_spinlock between them.
14 	A and each B is preceded by either A or C.  Moments when we enter
37 	* in ps_tq_int(): from the moment when we get ps_spinlock() to the
73 	   we would have to be called for the PIA that got ->claimed_cont
83 	it is holding pd_lock.	The only place within the area where we
87 	we were acquiring the lock, (1) would be already false, since
89 	If it was 0 before we tried to acquire pd_lock, (2) would be
96 (4) is done the same way - all places where we release pi_spinlock within
100 in the area, under pi_spinlock and we do not release it until after leaving
106 Corollary 1: ps_tq_active can be killed.  Indeed, the only place where we
108 point, we would have violated either (2.1) (if it was set while ps_set_intr()
109 was acquiring ps_spinlock) or (2.3) (if it was set when we started to
118 can be killed.  Indeed, we are not holding pd_lock and thus pd_busy is already
123 We don't need to reset it to NULL, since we are guaranteed that there
124 will be a call of ps_set_intr() before we look at ps_continuation again.
127 we never pass it NULL.  Assignements in the beginning of ps_set_intr()