Lines Matching full:callbacks

133 Once a CPU has been logically shutdown the teardown callbacks of registered
158 When a CPU is onlined, the startup callbacks are invoked sequentially until
160 callbacks of a state are set up or an instance is added to a multi-instance
163 When a CPU is offlined the teardown callbacks are invoked in the reverse
165 be invoked when the callbacks of a state are removed or an instance is
179   The startup callbacks in this section are invoked before the CPU is
180   started during a CPU online operation. The teardown callbacks are invoked
183   The callbacks are invoked on a control CPU as they can't obviously run on
187   The startup callbacks are used to setup resources which are required to
188   bring a CPU successfully online. The teardown callbacks are used to free
192   The startup callbacks are allowed to fail. If a callback fails, the CPU
196   The teardown callbacks in this section are not allowed to fail.
203   The startup callbacks in this section are invoked on the hotplugged CPU
205   setup code. The teardown callbacks are invoked with interrupts disabled
209   The callbacks in this section are not allowed to fail.
211   The callbacks are used for low level hardware initialization/shutdown and
219   The startup callbacks in this section are invoked on the hotplugged CPU
220   during a CPU online operation. The teardown callbacks are invoked on the
223   The callbacks are invoked in the context of the per CPU hotplug thread,
224   which is pinned on the hotplugged CPU. The callbacks are invoked with
227   The callbacks are allowed to fail. When a callback fails the hotplug
348   callbacks during a CPU online operation. During a CPU offline operation
349   the driver teardown callbacks have to be invoked before the core teardown
357   Static allocation is also required when the state callbacks are not set
363   When there are no ordering requirements for the state callbacks then
368   range. The STARTING section does not as most of the callbacks in that
382 CPU hotplug state callbacks need to be invoked for each instance, the CPU
386 invocations of the state callbacks on add and removal. To set up such a
432 The functions differ in the way how the installed callbacks are treated:
435     and cpuhp_setup_state_multi() only install the callbacks
438     callbacks and invoke the @startup callback (if not NULL) for all online
446     the callbacks for the state are not installed and in case of dynamic
452 used. These functions cannot be used from within CPU hotplug callbacks.
461            the state callbacks have to be removed later, e.g. module
486 The functions differ in the way how the installed callbacks are treated:
489     and cpuhp_remove_multi_state() only remove the callbacks.
491   * cpuhp_remove_state() removes the callbacks and invokes the teardown
503 used. These functions cannot be used from within CPU hotplug callbacks.
522 state callbacks and can be used by the callback to retrieve the instance
525 The functions differ in the way how the installed callbacks are treated:
551 The functions differ in the way how the installed callbacks are treated:
568 from within CPU hotplug callbacks and CPU hotplug read locked regions.
592 for notifications on online operations without invoking the callbacks::
690 95.552. All invoked callbacks including their return codes are visible in the