Lines Matching refs:callbacks

148 Once a CPU has been logically shutdown the teardown callbacks of registered
173 When a CPU is onlined, the startup callbacks are invoked sequentially until
175 callbacks of a state are set up or an instance is added to a multi-instance
178 When a CPU is offlined the teardown callbacks are invoked in the reverse
180 be invoked when the callbacks of a state are removed or an instance is
194   The startup callbacks in this section are invoked before the CPU is
195   started during a CPU online operation. The teardown callbacks are invoked
198   The callbacks are invoked on a control CPU as they can't obviously run on
202   The startup callbacks are used to setup resources which are required to
203   bring a CPU successfully online. The teardown callbacks are used to free
207   The startup callbacks are allowed to fail. If a callback fails, the CPU
211   The teardown callbacks in this section are not allowed to fail.
218   The startup callbacks in this section are invoked on the hotplugged CPU
220   setup code. The teardown callbacks are invoked with interrupts disabled
224   The callbacks in this section are not allowed to fail.
226   The callbacks are used for low level hardware initialization/shutdown and
234   The startup callbacks in this section are invoked on the hotplugged CPU
235   during a CPU online operation. The teardown callbacks are invoked on the
238   The callbacks are invoked in the context of the per CPU hotplug thread,
239   which is pinned on the hotplugged CPU. The callbacks are invoked with
242   The callbacks are allowed to fail. When a callback fails the hotplug
363   callbacks during a CPU online operation. During a CPU offline operation
364   the driver teardown callbacks have to be invoked before the core teardown
372   Static allocation is also required when the state callbacks are not set
378   When there are no ordering requirements for the state callbacks then
383   range. The STARTING section does not as most of the callbacks in that
397 CPU hotplug state callbacks need to be invoked for each instance, the CPU
401 invocations of the state callbacks on add and removal. To set up such a
447 The functions differ in the way how the installed callbacks are treated:
450     and cpuhp_setup_state_multi() only install the callbacks
453     callbacks and invoke the @startup callback (if not NULL) for all online
461     the callbacks for the state are not installed and in case of dynamic
467 used. These functions cannot be used from within CPU hotplug callbacks.
476            the state callbacks have to be removed later, e.g. module
501 The functions differ in the way how the installed callbacks are treated:
504     and cpuhp_remove_multi_state() only remove the callbacks.
506   * cpuhp_remove_state() removes the callbacks and invokes the teardown
518 used. These functions cannot be used from within CPU hotplug callbacks.
537 state callbacks and can be used by the callback to retrieve the instance
540 The functions differ in the way how the installed callbacks are treated:
566 The functions differ in the way how the installed callbacks are treated:
583 from within CPU hotplug callbacks and CPU hotplug read locked regions.
607 for notifications on online operations without invoking the callbacks::
705 95.552. All invoked callbacks including their return codes are visible in the