Lines Matching refs:can

2 	If ps_tq is scheduled, ps_tq_active is 1.  ps_tq_int() can be called
5 	under ps_spinlock.  There are three places where that can happen:
7 	Consider the sequnce of these events.  A can not be preceded by
9 	ps_spinlock.  C is always preceded by B, since we can't reach it
11 	IOW, the sequence is A?(BA|BC|B)*.  OTOH, number of B can not exceed
16 	since at any time number of B can not exceed the number of these
17 	moments which, in turn, can not exceed the number of A and C.
49 	1) at any time at most one thread of execution can be in that area or
60 (1) can become not true if some thread enters that area while another is 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
68 	d) ps_tq_int() can enter the area only when the thread is holding
77 	f) pi_wake_up() can enter the area only when the thread is holding
81 (2) can become not true only when pd_lock is released by the thread in question.
92 For similar reasons, (3) can become not true only when ps_spinlock is released
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
125 We can remove the check for ps_continuation being NULL for the same
128 can be taken to callers as long as they remain within the area.