Lines Matching defs:call_rcu

2001 	// Someone like call_rcu() requested a force-quiescent-state scan.
2555 	 * races with call_rcu() from interrupt handlers.  Leave the
2661 	 * The following usually indicates a double call_rcu().  To track
2999  * Handle any core-RCU processing required by a call_rcu() invocation.
3110 		 * Probable double call_rcu(), so leak the callback.
3112 		 * time callback was passed to call_rcu().
3133 		// This can trigger due to call_rcu() from offline CPU:
3167  * Use this API instead of call_rcu() if you don't want the callback to be
3172  * reuses call_rcu()'s logic. Refer to call_rcu() for more details about memory
3185  * call_rcu() - Queue an RCU callback for invocation after a grace period.
3197  * that started after call_rcu() was invoked.
3217  * to call_rcu().  It also means that each CPU executing an RCU read-side
3219  * executed a memory barrier after the call_rcu() but before the beginning
3224  * Furthermore, if CPU A invoked call_rcu() and CPU B invoked the
3227  * between the call to call_rcu() and the invocation of "func()" -- even
3234  * Specific to call_rcu() (as opposed to the other call_rcu*() functions),
3235  * in kernels built with CONFIG_RCU_LAZY=y, call_rcu() might delay for many
3241 void call_rcu(struct rcu_head *head, rcu_callback_t func)
3245 EXPORT_SYMBOL_GPL(call_rcu);
3797  * rcu_barrier - Wait until all in-flight call_rcu() callbacks complete.