Lines Matching full:rcu
52 // not-yet-completed RCU grace periods.
161 * Note a quasi-voluntary context switch for RCU-tasks's benefit.
231 * rcu_trace_implies_rcu_gp - does an RCU Tasks Trace grace period imply an RCU grace period?
233 * As an accident of implementation, an RCU Tasks Trace grace period also
234 * acts as an RCU grace period. However, this could change at any time.
243 * cond_resched_tasks_rcu_qs - Report potential quiescent states to RCU
246 * report potential quiescent states to RCU-tasks even if the cond_resched()
265 #error "Unknown RCU implementation specified to kernel configuration"
360 * ("rcu: Reject RCU_LOCKDEP_WARN() false positives") for more detail.
376 "Illegal context switch in RCU read-side critical section"); in rcu_preempt_sleep_check()
387 "Illegal context switch in RCU-bh read-side critical section"); \
389 "Illegal context switch in RCU-sched read-side critical section"); \
403 * multiple pointers markings to match different RCU implementations
421 * unrcu_pointer - mark a pointer as not being RCU protected
427 #define unrcu_pointer(p) __unrcu_pointer(p, __UNIQUE_ID(rcu))
455 #define rcu_dereference_raw(p) __rcu_dereference_raw(p, __UNIQUE_ID(rcu))
458 * RCU_INITIALIZER() - statically initialize an RCU-protected global variable
464 * rcu_assign_pointer() - assign to RCU-protected pointer
468 * Assigns the specified value to the specified RCU-protected
469 * pointer, ensuring that any concurrent RCU readers will see
476 * will be dereferenced by RCU read-side code.
506 * rcu_replace_pointer() - replace an RCU pointer, returning its old value
507 * @rcu_ptr: RCU pointer, whose old value is returned
511 * Perform a replacement, where @rcu_ptr is an RCU-annotated
524 * rcu_access_pointer() - fetch RCU pointer with no dereferencing
527 * Return the value of the specified RCU-protected pointer, but omit the
528 * lockdep checks for being in an RCU read-side critical section. This is
530 * not dereferenced, for example, when testing an RCU-protected pointer
534 * Within an RCU read-side critical section, there is little reason to
545 * the case in the context of the RCU callback that is freeing up the data,
550 #define rcu_access_pointer(p) __rcu_access_pointer((p), __UNIQUE_ID(rcu), __rcu)
561 * An implicit check for being in an RCU read-side critical section
582 * which pointers are protected by RCU and checks that the pointer is
586 __rcu_dereference_check((p), __UNIQUE_ID(rcu), \
594 * This is the RCU-bh counterpart to rcu_dereference_check(). However,
595 * please note that starting in v5.0 kernels, vanilla RCU grace periods
602 __rcu_dereference_check((p), __UNIQUE_ID(rcu), \
610 * This is the RCU-sched counterpart to rcu_dereference_check().
611 * However, please note that starting in v5.0 kernels, vanilla RCU grace
618 __rcu_dereference_check((p), __UNIQUE_ID(rcu), \
623 * The tracing infrastructure traces RCU (we want that), but unfortunately
624 * some of the RCU checks causes tracing to lock up the system.
630 __rcu_dereference_check((p), __UNIQUE_ID(rcu), 1, __rcu)
633 * rcu_dereference_protected() - fetch RCU pointer when updates prevented
637 * Return the value of the specified RCU-protected pointer, but omit
649 __rcu_dereference_protected((p), __UNIQUE_ID(rcu), (c), __rcu)
653 * rcu_dereference() - fetch RCU-protected pointer for dereferencing
661 * rcu_dereference_bh() - fetch an RCU-bh-protected pointer for dereferencing
669 * rcu_dereference_sched() - fetch RCU-sched-protected pointer for dereferencing
677 * rcu_pointer_handoff() - Hand off a pointer from RCU to other mechanism
681 * is handed off from RCU to some other synchronization mechanism, for
699 * rcu_read_lock() - mark the beginning of an RCU read-side critical section
702 * are within RCU read-side critical sections, then the
705 * on one CPU while other CPUs are within RCU read-side critical
706 * sections, invocation of the corresponding RCU callback is deferred
715 * Note, however, that RCU callbacks are permitted to run concurrently
716 * with new RCU read-side critical sections. One way that this can happen
717 * is via the following sequence of events: (1) CPU 0 enters an RCU
719 * an RCU callback, (3) CPU 0 exits the RCU read-side critical section,
720 * (4) CPU 2 enters a RCU read-side critical section, (5) the RCU
721 * callback is invoked. This is legal, because the RCU read-side critical
723 * therefore might be referencing something that the corresponding RCU
725 * RCU callback is invoked.
727 * RCU read-side critical sections may be nested. Any deferred actions
728 * will be deferred until the outermost RCU read-side critical section
732 * following this rule: don't put anything in an rcu_read_lock() RCU
736 * In non-preemptible RCU implementations (pure TREE_RCU and TINY_RCU),
737 * it is illegal to block while in an RCU read-side critical section.
738 * In preemptible RCU implementations (PREEMPT_RCU) in CONFIG_PREEMPTION
739 * kernel builds, RCU read-side critical sections may be preempted,
740 * but explicit blocking is illegal. Finally, in preemptible RCU
741 * implementations in real-time (with -rt patchset) kernel builds, RCU
748 __acquire(RCU); in rcu_read_lock()
756 * way for writers to lock out RCU readers. This is a feature, not
757 * a bug -- this property is what provides RCU's performance benefits.
760 * used as well. RCU does not care how the writers keep out of each
765 * rcu_read_unlock() - marks the end of an RCU read-side critical section.
780 __release(RCU); in rcu_read_unlock()
786 * rcu_read_lock_bh() - mark the beginning of an RCU-bh critical section
789 * Note that anything else that disables softirqs can also serve as an RCU
809 * rcu_read_unlock_bh() - marks the end of a softirq-only RCU critical section
823 * rcu_read_lock_sched() - mark the beginning of a RCU-sched critical section
854 * rcu_read_unlock_sched() - marks the end of a RCU-classic critical section
875 * RCU_INIT_POINTER() - initialize an RCU protected pointer
879 * Initialize an RCU-protected pointer in special cases where readers
885 * RCU readers from concurrently accessing this pointer *or*
898 * will look OK in crash dumps, but any concurrent RCU readers might
902 * If you are creating an RCU-protected linked structure that is accessed
903 * by a single external-to-structure RCU-protected pointer, then you may
904 * use RCU_INIT_POINTER() to initialize the internal RCU-protected
919 * RCU_POINTER_INITIALIZER() - statically initialize an RCU protected pointer
923 * GCC-style initialization for an RCU-protected pointer in a structure field.
939 * Many rcu callbacks functions just call kfree() on the base structure.
1043 * in an RCU read-side critical section that includes a read-side fetch
1061 DEFINE_LOCK_GUARD_0(rcu, rcu_read_lock(), rcu_read_unlock())