Lines Matching full:rcu

4 RCU and lockdep checking
7 All flavors of RCU have lockdep checking available, so that lockdep is
8 aware of when each task enters and leaves any flavor of RCU read-side
9 critical section.  Each flavor of RCU is tracked separately (but note
11 tracking to include RCU state, which can sometimes help when debugging
14 In addition, RCU provides the following primitives that check lockdep's
17 	rcu_read_lock_held() for normal RCU.
18 	rcu_read_lock_bh_held() for RCU-bh.
19 	rcu_read_lock_sched_held() for RCU-sched.
20 	rcu_read_lock_any_held() for any of normal RCU, RCU-bh, and RCU-sched.
22 	rcu_read_lock_trace_held() for RCU Tasks Trace.
33 		Check for RCU read-side critical section.
35 		Check for RCU-bh read-side critical section.
37 		Check for RCU-sched read-side critical section.
43 		invoked by both RCU readers and updaters.
47 		is invoked by both RCU-bh readers and updaters.
51 		is invoked by both RCU-sched readers and updaters.
79 This expression picks up the pointer "fdt->fd[fd]" in an RCU-safe manner,
83 1.	An RCU read-side critical section (implicit), or
87 In case (1), the pointer is picked up in an RCU-safe manner for vanilla
88 RCU read-side critical sections, in case (2) the ->file_lock prevents
99 complain even if this was used in an RCU read-side critical section unless
103 to use rcu_dereference_protected() if either the RCU-protected pointer
104 or the RCU-protected data that it points to can change concurrently.
106 Like rcu_dereference(), when lockdep is enabled, RCU list and hlist
107 traversal primitives check for being called from within an RCU read-side
111 false and they are called from outside any RCU read-side critical section.
114 either within an RCU read-side critical section or with wq->mutex held.