Lines Matching full:rcu
126 * RCU_NONIDLE - Indicate idle-loop code that needs RCU readers
127 * @a: Code that RCU needs to pay attention to.
129 * RCU read-side critical sections are forbidden in the inner idle loop,
130 * that is, between the rcu_idle_enter() and the rcu_idle_exit() -- RCU
135 * will tell RCU that it needs to pay attention, invoke its argument
137 * and then tell RCU to go back to ignoring this CPU. It is permissible
151 * Note a quasi-voluntary context switch for RCU-tasks's benefit.
207 * cond_resched_tasks_rcu_qs - Report potential quiescent states to RCU
210 * report potential quiescent states to RCU-tasks even if the cond_resched()
229 #error "Unknown RCU implementation specified to kernel configuration"
328 "Illegal context switch in RCU read-side critical section"); in rcu_preempt_sleep_check()
339 "Illegal context switch in RCU-bh read-side critical section"); \
341 "Illegal context switch in RCU-sched read-side critical section"); \
355 * multiple pointers markings to match different RCU implementations
367 * unrcu_pointer - mark a pointer as not being RCU protected
408 * RCU_INITIALIZER() - statically initialize an RCU-protected global variable
414 * rcu_assign_pointer() - assign to RCU-protected pointer
418 * Assigns the specified value to the specified RCU-protected
419 * pointer, ensuring that any concurrent RCU readers will see
426 * will be dereferenced by RCU read-side code.
456 * rcu_replace_pointer() - replace an RCU pointer, returning its old value
457 * @rcu_ptr: RCU pointer, whose old value is returned
461 * Perform a replacement, where @rcu_ptr is an RCU-annotated
474 * rcu_access_pointer() - fetch RCU pointer with no dereferencing
477 * Return the value of the specified RCU-protected pointer, but omit the
478 * lockdep checks for being in an RCU read-side critical section. This is
480 * not dereferenced, for example, when testing an RCU-protected pointer
487 * is the case in the context of the RCU callback that is freeing up
503 * An implicit check for being in an RCU read-side critical section
524 * which pointers are protected by RCU and checks that the pointer is
535 * This is the RCU-bh counterpart to rcu_dereference_check(). However,
536 * please note that starting in v5.0 kernels, vanilla RCU grace periods
550 * This is the RCU-sched counterpart to rcu_dereference_check().
551 * However, please note that starting in v5.0 kernels, vanilla RCU grace
562 * The tracing infrastructure traces RCU (we want that), but unfortunately
563 * some of the RCU checks causes tracing to lock up the system.
571 * rcu_dereference_protected() - fetch RCU pointer when updates prevented
575 * Return the value of the specified RCU-protected pointer, but omit
591 * rcu_dereference() - fetch RCU-protected pointer for dereferencing
599 * rcu_dereference_bh() - fetch an RCU-bh-protected pointer for dereferencing
607 * rcu_dereference_sched() - fetch RCU-sched-protected pointer for dereferencing
615 * rcu_pointer_handoff() - Hand off a pointer from RCU to other mechanism
619 * is handed off from RCU to some other synchronization mechanism, for
637 * rcu_read_lock() - mark the beginning of an RCU read-side critical section
640 * are within RCU read-side critical sections, then the
643 * on one CPU while other CPUs are within RCU read-side critical
644 * sections, invocation of the corresponding RCU callback is deferred
653 * Note, however, that RCU callbacks are permitted to run concurrently
654 * with new RCU read-side critical sections. One way that this can happen
655 * is via the following sequence of events: (1) CPU 0 enters an RCU
657 * an RCU callback, (3) CPU 0 exits the RCU read-side critical section,
658 * (4) CPU 2 enters a RCU read-side critical section, (5) the RCU
659 * callback is invoked. This is legal, because the RCU read-side critical
661 * therefore might be referencing something that the corresponding RCU
663 * RCU callback is invoked.
665 * RCU read-side critical sections may be nested. Any deferred actions
666 * will be deferred until the outermost RCU read-side critical section
670 * following this rule: don't put anything in an rcu_read_lock() RCU
674 * In non-preemptible RCU implementations (pure TREE_RCU and TINY_RCU),
675 * it is illegal to block while in an RCU read-side critical section.
676 * In preemptible RCU implementations (PREEMPT_RCU) in CONFIG_PREEMPTION
677 * kernel builds, RCU read-side critical sections may be preempted,
678 * but explicit blocking is illegal. Finally, in preemptible RCU
679 * implementations in real-time (with -rt patchset) kernel builds, RCU
686 __acquire(RCU); in rcu_read_lock()
694 * way for writers to lock out RCU readers. This is a feature, not
695 * a bug -- this property is what provides RCU's performance benefits.
698 * used as well. RCU does not care how the writers keep out of each
703 * rcu_read_unlock() - marks the end of an RCU read-side critical section.
718 __release(RCU); in rcu_read_unlock()
724 * rcu_read_lock_bh() - mark the beginning of an RCU-bh critical section
727 * Note that anything else that disables softirqs can also serve as an RCU
747 * rcu_read_unlock_bh() - marks the end of a softirq-only RCU critical section
761 * rcu_read_lock_sched() - mark the beginning of a RCU-sched critical section
792 * rcu_read_unlock_sched() - marks the end of a RCU-classic critical section
813 * RCU_INIT_POINTER() - initialize an RCU protected pointer
817 * Initialize an RCU-protected pointer in special cases where readers
823 * RCU readers from concurrently accessing this pointer *or*
836 * will look OK in crash dumps, but any concurrent RCU readers might
840 * If you are creating an RCU-protected linked structure that is accessed
841 * by a single external-to-structure RCU-protected pointer, then you may
842 * use RCU_INIT_POINTER() to initialize the internal RCU-protected
857 * RCU_POINTER_INITIALIZER() - statically initialize an RCU protected pointer
861 * GCC-style initialization for an RCU-protected pointer in a structure field.
878 * Many rcu callbacks functions just call kfree() on the base structure.
990 * in an RCU read-side critical section that includes a read-side fetch