42  * Check the RCU kernel configuration parameters and print informative
54 		pr_info("\tHierarchical RCU autobalancing is disabled.\n");  in rcu_bootup_announce_oddness()
120  * Tell them what RCU they are running.
124 	pr_info("Preemptible hierarchical RCU implementation.\n");  in rcu_bootup_announce()
135  * Queues a task preempted within an RCU-preempt read-side critical
157  * their RCU read-side critical sections.  At that point, the ->gp_tasks
174 	/* RCU better not be waiting on newly onlined CPUs! */  in rcu_preempt_ctxt_queue()
281  * Record a preemptible-RCU quiescent state for the specified CPU.
284  * grace period need not wait on any RCU read-side critical section that
286  * in an RCU read-side critical section, it has already added itself to
289  * in an RCU read-side critical section.
291  * Unlike non-preemptible-RCU, quiescent state reports for expedited
312  * context-switched away from.  If this task is in an RCU read-side
316  * RCU read-side critical section.  Therefore, the current grace period
331 …WARN_ONCE(!preempt && rcu_preempt_depth() > 0, "Voluntary context switch within RCU read-side crit…  in rcu_note_context_switch()
335 		/* Possibly blocking in an RCU read-side critical section. */  in rcu_note_context_switch()
359 	 * Either we were not in an RCU read-side critical section to  in rcu_note_context_switch()
362 	 * for this CPU.  Again, if we were in an RCU read-side critical  in rcu_note_context_switch()
376  * Check for preempted RCU readers blocking the current grace period
407  * Preemptible RCU implementation for rcu_read_lock().
423  * Preemptible RCU implementation for rcu_read_unlock().
427  * in an RCU read-side critical section and other special cases.
464  * preempted within an RCU read-side critical section.
489 	 * If RCU core is waiting for this CPU to exit its critical section,  in rcu_preempt_deferred_qs_irqrestore()
519 	/* Clean up if blocked during RCU read-side critical section. */  in rcu_preempt_deferred_qs_irqrestore()
536 		smp_mb(); /* ensure expedited fastpath sees end of RCU c-s. */  in rcu_preempt_deferred_qs_irqrestore()
590  * an RCU read-side critical section?  It is the caller's responsibility
607  * not being in an RCU read-side critical section.  The caller must
634  * notify RCU core processing or task having blocked during the RCU
698  * period that still has RCU readers blocked!  This function must be
725  * context switches for Tasks RCU.  When a task blocks, the task is
760  * Check for a task exiting while in a preemptible-RCU read-side
845  * Tell them what RCU they are running.
849 	pr_info("Hierarchical RCU implementation.\n");  in rcu_bootup_announce()
921  * Because preemptible RCU does not exist, there are never any preempted
922  * RCU readers.
930  * Because there is no preemptible RCU, there can be no readers blocked.
938  * Because there is no preemptible RCU, there can be no deferred quiescent
948 // non-preemptible kernels, there can be no context switches within RCU
962  * Because there is no preemptible RCU, there can be no readers blocked,
995  * Because preemptible RCU does not exist, tasks cannot possibly exit
996  * while in preemptible RCU read-side critical sections.
1039  * Is the current CPU running the RCU-callbacks kthread?
1051  * Carry out RCU priority boosting on the task indicated by ->exp_tasks
1072 	 * might exit their RCU read-side critical sections on their own.  in rcu_boost()
1094 	 * exits its outermost RCU read-side critical section.  Then  in rcu_boost()
1103 	 * and task t's exiting its outermost RCU read-side critical  in rcu_boost()
1154  * Check to see if it is time to start boosting RCU readers that are
1199  * Create an RCU-boost kthread for the specified node if one does not
1200  * already exist.  We only create this kthread for preemptible RCU.
1253  * Is this CPU a NO_HZ_FULL CPU that should ignore RCU so that the
1255  * The idea is to avoid waking up RCU core processing on such a
1273  * Bind the RCU grace-period kthreads to the housekeeping CPU.