Lines Matching full:side
154 * RCU read-side critical sections are forbidden in the inner idle loop,
156 * will happily ignore any such read-side critical sections. However,
365 "Illegal context switch in RCU read-side critical section"); in rcu_preempt_sleep_check()
376 "Illegal context switch in RCU-bh read-side critical section"); \
378 "Illegal context switch in RCU-sched read-side critical section"); \
465 * will be dereferenced by RCU read-side code.
517 * lockdep checks for being in an RCU read-side critical section. This is
521 * where update-side locks prevent the value of the pointer from changing,
523 * Within an RCU read-side critical section, there is little reason to
532 * It is also permissible to use rcu_access_pointer() when read-side
550 * An implicit check for being in an RCU read-side critical section
627 * the READ_ONCE(). This is useful in cases where update-side locks
633 * This function is only for update-side use. Using this function
688 * rcu_read_lock() - mark the beginning of an RCU read-side critical section
691 * are within RCU read-side critical sections, then the
694 * on one CPU while other CPUs are within RCU read-side critical
705 * with new RCU read-side critical sections. One way that this can happen
707 * read-side critical section, (2) CPU 1 invokes call_rcu() to register
708 * an RCU callback, (3) CPU 0 exits the RCU read-side critical section,
709 * (4) CPU 2 enters a RCU read-side critical section, (5) the RCU
710 * callback is invoked. This is legal, because the RCU read-side critical
716 * RCU read-side critical sections may be nested. Any deferred actions
717 * will be deferred until the outermost RCU read-side critical section
722 * read-side critical section that would block in a !PREEMPTION kernel.
726 * it is illegal to block while in an RCU read-side critical section.
728 * kernel builds, RCU read-side critical sections may be preempted,
731 * read-side critical sections may be preempted and they may also block, but
754 * rcu_read_unlock() - marks the end of an RCU read-side critical section.
779 * read-side critical section. However, please note that this equivalence
815 * Read-side critical sections can also be introduced by anything else that
1041 * in an RCU read-side critical section that includes a read-side fetch