include/linux/rcupdate.h

125  * RCU read-side critical sections are forbidden in the inner idle loop,
127  * will happily ignore any such read-side critical sections.  However,
323 			 "Illegal context switch in RCU read-side critical section");  in rcu_preempt_sleep_check()
333 				 "Illegal context switch in RCU-bh read-side critical section"); \
335 				 "Illegal context switch in RCU-sched read-side critical section"); \
458  * lockdep checks for being in an RCU read-side critical section.  This is
483  * An implicit check for being in an RCU read-side critical section
607  * rcu_read_lock() - mark the beginning of an RCU read-side critical section
610  * are within RCU read-side critical sections, then the
612  * CPUs exit their critical sections.  Similarly, if call_rcu() is invoked
613  * on one CPU while other CPUs are within RCU read-side critical
615  * until after the all the other CPUs exit their critical sections.
618  * with new RCU read-side critical sections.  One way that this can happen
620  * read-side critical section, (2) CPU 1 invokes call_rcu() to register
621  * an RCU callback, (3) CPU 0 exits the RCU read-side critical section,
622  * (4) CPU 2 enters a RCU read-side critical section, (5) the RCU
623  * callback is invoked.  This is legal, because the RCU read-side critical
629  * RCU read-side critical sections may be nested.  Any deferred actions
630  * will be deferred until the outermost RCU read-side critical section
635  * read-side critical section that would block in a !PREEMPTION kernel.
639  * it is illegal to block while in an RCU read-side critical section.
641  * kernel builds, RCU read-side critical sections may be preempted,
644  * read-side critical sections may be preempted and they may also block, but
667  * rcu_read_unlock() - marks the end of an RCU read-side critical section.
679  * that preemption never happens within any RCU read-side critical
683  * critical section's outermost rcu_read_lock().
687  * that that preemption never happens within any RCU read-side critical
709  * rcu_read_lock_bh() - mark the beginning of an RCU-bh critical section
713  * an RCU read-side critical section.
730  * rcu_read_unlock_bh() - marks the end of a softirq-only RCU critical section
744  * rcu_read_lock_sched() - mark the beginning of a RCU-sched critical section
747  * Read-side critical sections can also be introduced by anything else
772  * rcu_read_unlock_sched() - marks the end of a RCU-classic critical section
974  * in an RCU read-side critical section that includes a read-side fetch