Lines Matching refs:be

2 	If ps_tq is scheduled, ps_tq_active is 1.  ps_tq_int() can be called
7 	Consider the sequnce of these events.  A can not be preceded by
49 	1) at any time at most one thread of execution can be in that area or
50 	be preempted there.
61 	a) do_pd_request1() can be called from next_request() or do_pd_request()
65 	b) ps_set_intr() and pi_schedule_claimed() can be called only from the
71 	e) do_pd_{read,write}* could be called only from the area.  The only
73 	   we would have to be called for the PIA that got ->claimed_cont
85 	But that code does not reset pd_busy, so pd_busy would have to be
87 	we were acquiring the lock, (1) would be already false, since
88 	the thread that had reset it would be in the area simulateously.
89 	If it was 0 before we tried to acquire pd_lock, (2) would be
106 Corollary 1: ps_tq_active can be killed.  Indeed, the only place where we
112 Corollary 2: ps_spinlock can be killed.  Indeed, Lemma 1 and Lemma 2 show
118 can be killed.  Indeed, we are not holding pd_lock and thus pd_busy is already
121 Corollary 4: in ps_tq_int() uses of con can be replaced with uses of
124 will be a call of ps_set_intr() before we look at ps_continuation again.
126 reason - the value is guaranteed to be set by the last ps_set_intr() and
128 can be taken to callers as long as they remain within the area.