Lines Matching full:hot

6 to handle hot plugging of dynamic "physical" resources like PCI cards, or
17 To manage hot plug/unplug of these resources, a firmware abstraction known as
31 such as the DRCs managing PCI slots on a hot plugged PHB. In this case the
33 for hot plugged resources described under :ref:`guest-host-interface`.
185     ``2``: ``identify``, used to visually identify slot for interactive hot plug.
193   hot plug/unplug) the pre-allocation of the resource is implied and this sensor
312 Hot plug/unplug events
329 :ref:`hot-plug-unplug-event-structure`. Note that these events are not formally
331 also described below under :ref:`hot-plug-unplug-event-structure`, and so are
343 addition of a ``hot-plug-events`` node under ``/event-sources`` node of the
349 Hot plug/unplug event structure
352 The hot plug specific payload in QEMU is implemented as follows (with all values
433   memory can be hot-plugged to the guest.