Lines Matching refs:IPI

27 each of which results in an IPI to the target CPU.
48 The dotted arrows denote indirect action, for example, an IPI
55 ``smp_call_function_single()`` to send the CPU an IPI, which
96 | IPI the CPU to safely interact with the upcoming                      |
105 | IPI the CPU.                                                          |
128 that the CPU went idle while the IPI was in flight. If the CPU is idle,
142 grace periods. In addition, attempting to IPI offline CPUs will result
143 in splats, but failing to IPI online CPUs can result in too-short grace
231 For RCU-sched, there is an additional check: If the IPI has interrupted
235 For RCU-preempt, there is no specific check for idle in the IPI handler
245 bitmask of CPUs that must be IPIed, just before sending each IPI, and
246 (either explicitly or implicitly) within the IPI handler.
508 different IPI handlers and different code to respond to the state