Lines Matching defs:call_rcu
1580 // Someone like call_rcu() requested a force-quiescent-state scan.
2146 * races with call_rcu() from interrupt handlers. Leave the
2252 * The following usually indicates a double call_rcu(). To track
2614 * Handle any core-RCU processing required by a call_rcu() invocation.
2721 * Probable double call_rcu(), so leak the callback.
2723 * time callback was passed to call_rcu().
2741 // This can trigger due to call_rcu() from offline CPU:
2775 * Use this API instead of call_rcu() if you don't want the callback to be
2780 * reuses call_rcu()'s logic. Refer to call_rcu() for more details about memory
2793 * call_rcu() - Queue an RCU callback for invocation after a grace period.
2805 * that started after call_rcu() was invoked.
2819 * to call_rcu(). It also means that each CPU executing an RCU read-side
2821 * executed a memory barrier after the call_rcu() but before the beginning
2826 * Furthermore, if CPU A invoked call_rcu() and CPU B invoked the
2829 * between the call to call_rcu() and the invocation of "func()" -- even
2836 void call_rcu(struct rcu_head *head, rcu_callback_t func)
2840 EXPORT_SYMBOL_GPL(call_rcu);
4055 * rcu_barrier - Wait until all in-flight call_rcu() callbacks complete.