Lines Matching full:resources

6 to handle hot plugging of dynamic "physical" resources like PCI cards, or
7 "logical"/para-virtual resources like memory, CPUs, and "physical"
9 to guests as virtualized resources. The specifics of dynamic reconfiguration
17 To manage hot plug/unplug of these resources, a firmware abstraction known as
33 for hot plugged resources described under :ref:`guest-host-interface`.
46     ``<name>`` values for logical/virtual resources are defined in the Linux on
49     value that's unique across resources of that type.
51     ``<name>`` values for "physical" resources such as PCI or VIO devices are
55     resources to a physical location in a chassis for debugging purposes. For
88       across all resources of specified type.
97   associated all resources with a "live insertion" domain, where the power is
122 Guest->Host interface to manage dynamic resources
125 Each DRC is given a globally unique DRC index, and resources associated with a
189 * ``9003``: ``allocation-state``, generally only used for "logical" DR resources
229     For physical resources: DRC/slot is empty.
231     For logical resources: unused.
235     For physical resources: DRC/slot is populated with a device/resource.
237     For logical resources: resource has been allocated to the DRC.
241     For physical resources: unused.
243     For logical resources: DRC has no resource allocated to it.
247     For physical resources: unused.
249     For logical resources: resource available for exchange (see
254     For physical resources: unused.
256     For logical resources: resource available for recovery (see
400            uint32_t count;                 /* number of DR resources to take
405                uint32_t count;             /* number of DR resources to take