Lines Matching full:rcu

7 important to correct use of things like RCU.  To this end, the pointers
24 from your calls to rcu_dereference() and friends, thus keeping your RCU
28 	to load an RCU-protected pointer, otherwise CONFIG_PROVE_RCU
80 -	If you are using RCU to protect JITed functions, so that the
143 		RCU-protected circular linked lists.
146 		of an RCU read-side critical section, and the pointer
153 		Within an RCU read-side critical section, there is little
185 		That said, this situation can make certain RCU usage
188 		of such an RCU usage bug is shown in the section titled
189 		"EXAMPLE OF AMPLIFIED RCU-USAGE BUG".
219 EXAMPLE OF AMPLIFIED RCU-USAGE BUG
222 Because updaters can run concurrently with RCU readers, RCU readers can
223 see stale and/or inconsistent values.  If RCU readers need fresh or
348 guarantees that RCU depends on.  And the volatile cast in rcu_dereference()
406 1.	If the access needs to be within an RCU read-side critical
408 	RCU flavors, an RCU read-side critical section is entered
412 	are also implied RCU read-side critical sections, even when
416 2.	If the access might be within an RCU read-side critical section
424 3.	If the access might be within an RCU read-side critical section
457 SPARSE CHECKING OF RCU-PROTECTED POINTERS
460 The sparse static-analysis tool checks for non-RCU access to RCU-protected