Lines Matching full:side
115 * RCU read-side critical sections are forbidden in the inner idle loop,
117 * will happily ignore any such read-side critical sections. However,
313 "Illegal context switch in RCU read-side critical section"); in rcu_preempt_sleep_check()
323 "Illegal context switch in RCU-bh read-side critical section"); \
325 "Illegal context switch in RCU-sched read-side critical section"); \
396 * will be dereferenced by RCU read-side code.
448 * lockdep checks for being in an RCU read-side critical section. This is
452 * where update-side locks prevent the value of the pointer from changing,
455 * It is also permissible to use rcu_access_pointer() when read-side
473 * An implicit check for being in an RCU read-side critical section
536 * the READ_ONCE(). This is useful in cases where update-side locks
542 * This function is only for update-side use. Using this function
597 * rcu_read_lock() - mark the beginning of an RCU read-side critical section
600 * are within RCU read-side critical sections, then the
603 * on one CPU while other CPUs are within RCU read-side critical
608 * with new RCU read-side critical sections. One way that this can happen
610 * read-side critical section, (2) CPU 1 invokes call_rcu() to register
611 * an RCU callback, (3) CPU 0 exits the RCU read-side critical section,
612 * (4) CPU 2 enters a RCU read-side critical section, (5) the RCU
613 * callback is invoked. This is legal, because the RCU read-side critical
619 * RCU read-side critical sections may be nested. Any deferred actions
620 * will be deferred until the outermost RCU read-side critical section
625 * read-side critical section that would block in a !PREEMPTION kernel.
629 * it is illegal to block while in an RCU read-side critical section.
631 * kernel builds, RCU read-side critical sections may be preempted,
634 * read-side critical sections may be preempted and they may also block, but
657 * rcu_read_unlock() - marks the end of an RCU read-side critical section.
669 * that preemption never happens within any RCU read-side critical
677 * that that preemption never happens within any RCU read-side critical
703 * an RCU read-side critical section.
737 * Read-side critical sections can also be introduced by anything else
964 * in an RCU read-side critical section that includes a read-side fetch