Lines Matching full:area
23 consider the following area:
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.
62 In the first case the thread was already in the area. In the second,
66 area.
67 c) pi_do_claimed() is called by pd.c only from the area.
68 d) ps_tq_int() can enter the area only when the thread is holding
71 e) do_pd_{read,write}* could be called only from the area. The only
77 f) pi_wake_up() can enter the area only when the thread is holding
82 Indeed, pd_busy is reset only in the area and thread that resets
83 it is holding pd_lock. The only place within the area where we
84 release pd_lock is in pd_next_buf() (called from within the area).
88 the thread that had reset it would be in the area simulateously.
93 by the thread in question. However, all such places within the area are right
97 the area are either after resetting ->claimed_cont to NULL while holding
99 also in the area. The only place where ->claimed_cont is made non-NULL is
100 in the area, under pi_spinlock and we do not release it until after leaving
101 the area.
122 ps_continuation, since the latter is changed only from the area.
128 can be taken to callers as long as they remain within the area.