Lines Matching full:for
19 resource to the guest, and provide an interface for the guest to manage
33 for hot plugged resources described under :ref:`guest-host-interface`.
46 ``<name>`` values for logical/virtual resources are defined in the Linux on
51 ``<name>`` values for "physical" resources such as PCI or VIO devices are
54 for the device, concatenated by a hyphen. This provides a mapping of
55 resources to a physical location in a chassis for debugging purposes. For
57 conforms to naming specifications, but is simply a location label for the
58 slot by itself to simplify the implementation. The naming convention for
60 and in our case amounts to using ``C<n>`` for PCI/VIO device slots, where
77 ``1`` for CPU resource.
79 ``2`` for PHB resource.
81 ``3`` for VIO resource.
83 ``4`` for PCI resource.
85 ``8`` for memory resource.
98 assumed to be managed automatically. The integer value for this domain is a
110 "CPU" for a CPU.
112 "PHB" for a physical host-bridge.
114 "SLOT" for a VIO slot.
116 "28" for a PCI slot.
118 "MEM" for memory resource.
133 Set the power level for a specified power domain.
137 ``arg[1]``: new power level for the domain, ``0-100``.
146 Get the power level for a specified power domain.
161 ``arg[1]``: index of sensor, for DR-related sensors this is generally the DRC
168 For the purpose of this document we focus on the indicator/sensor types
185 ``2``: ``identify``, used to visually identify slot for interactive hot plug.
189 * ``9003``: ``allocation-state``, generally only used for "logical" DR resources
192 ``isolation-state->isolate``, respectively. For "physical" DR (like PCI
199 ``1``: ``usable``, request the resource be allocated/reserved for use by
202 ``2``: ``exchange``, used to allocate a spare resource to use for fail-over
215 ``arg[1]``: index of sensor, for DR-related sensors this is generally the DRC
220 For DR-related operations, the only noteworthy sensor is ``dr-entity-sense``,
225 Supported sensor values for ``dr-entity-sense`` (``9003``) sensor:
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
268 non-zero if a prior RTAS response indicated a need for additional memory.
274 ``1``: instruct guest to prepare for next device tree sibling node.
276 ``2``: instruct guest to prepare for next device tree child node.
278 ``3``: instruct guest to prepare for next device tree property.
296 For next-sibling/next-child response:
300 For next-property response:
304 ``wa[3]``: for next-property response (unused otherwise):
308 ``wa[4]``: for next-property response (unused otherwise):
315 For most DR operations, the hypervisor will issue host->guest add/remove events
319 documented by PAPR+ v2.7, and already use in by QEMU for generating powerdown
322 For DR, this framework has been extended to include hotplug events, which were
325 applicable to KVM on Power, hence the reason for extending the notification
328 The format for these EPOW-signalled events is described below under
333 contains additional fields/flags, which are denoted for the purposes of this
336 QEMU should assume support only for "legacy" fields/flags unless the guest
337 advertises support for the "modern" format via
364 * specified for hotplug_identifier
387 * for the 'drc' union field below
438 ``pseries`` guests use this property to note the maximum allowed CPUs for the
446 only when the guest advertises the support for it via
461 information for each LMB can be found. It is a property encoded array
469 associativity list to use for the LMB. This index value for each LMB is defined
485 - Four bytes reserved for expansion.
486 - Associativity list index for the LMB that is used as an index into
488 to retrieve the right associativity list to be used for this LMB.
499 for each sequential group of LMBs that share common attributes.
508 is used to retrieve the right associativity list to be used for all