Lines Matching full:assigned
10 The AP devices provide cryptographic functions to all CPUs assigned to a
27 functions. There can be from 0 to 256 adapters assigned to an LPAR. Adapters
28 assigned to the LPAR in which a linux host is running will be available to
34 The AP adapter cards are assigned to a given LPAR via the system's Activation
36 in the LPAR, the AP bus detects the AP adapter cards assigned to the LPAR and
37 creates a sysfs device for each assigned adapter. For example, if AP adapters
38 4 and 10 (0x0a) are assigned to the LPAR, the AP bus will create the following
68 The AP usage and control domains are assigned to a given LPAR via the system's
71 domains assigned to the LPAR. The domain number of each usage domain and
91 domains 6 and 71 (0x47) are assigned to the LPAR, the AP bus will create the
128 control domains assigned to the KVM guest:
130 * The AP Mask (APM) field is a bit mask that identifies the AP adapters assigned
136 assigned to the KVM guest. Each bit in the mask, from left to right,
141 assigned to the KVM guest. The ADM bit mask controls which domains can be
151 calculated from the APM and AQM; it is the Cartesian product of all assigned
152 adapter numbers (APM) with all assigned queue indexes (AQM). For example, if
153 adapters 1 and 2 and usage domains 5 and 6 are assigned to a guest, the APQNs
157 on the adapter card for each of its domains - so each APQN must be assigned to
366 product of the adapter and domain numbers assigned to the vfio_ap mediated
370 product of the adapter and domain numbers assigned to the APM and AQM
372 the APQNs assigned to the vfio_ap mediated device if any APQN does not
378 the ID of the domain to be assigned/unassigned is echoed into the
381 A read-only file for displaying the control domain numbers assigned to the
396 and control domains should be assigned to the mediated device.
421 domains assigned via the corresponding sysfs attributes files
457 * Setting the bits in the APM corresponding to the APIDs assigned to the
459 * Setting the bits in the AQM corresponding to the domains assigned to the
461 * Setting the bits in the ADM corresponding to the domain dIDs assigned to the
467 driver will not be assigned to a KVM guest's matrix. The AP architecture,
469 matrix, so the adapters, domains and control domains assigned to vfio_ap
475 the control domains assigned to the matrix mdev that are not also assigned to
478 * Each APQN derived from the Cartesian product of the APIDs and APQIs assigned
647 The APQN of each AP queue device assigned to the linux host is checked by the
717 the vfio_ap mediated device to which it is assigned; for example:
719 … Userspace may not re-assign queue 05.0054 already assigned to 62177883-f1bb-47f0-914d-32a22e3a8804
720 … Userspace may not re-assign queue 04.0054 already assigned to cef03c3c-903d-4ecc-9a83-40694cb8aee4
844 Control domains can similarly be assigned using the assign_control_domain
855 To display the matrix that is or will be assigned to Guest1::
882 being assigned and the APQIs of the domains previously assigned:
889 - Must NOT be assigned to another vfio_ap mediated device. If even one APQN
890 is assigned to another vfio_ap mediated device, the operation will
893 - Must NOT be assigned while the sysfs /sys/bus/ap/apmask and
908 being assigned and the APIDs of the adapters previously assigned:
915 - Must NOT be assigned to another vfio_ap mediated device. If even one APQN
916 is assigned to another vfio_ap mediated device, the operation will
919 - Must NOT be assigned while the sysfs /sys/bus/ap/apmask and
976 * The adapter, domain or control domain must also be assigned to the host's
980 adapter being assigned and the APQIs of the domains assigned must reference a
984 comprised of the APQI of the domain being assigned and the APIDs of the
985 adapters assigned must reference a queue device bound to the vfio_ap device
998 the vfio_ap mediated device to which it is assigned as long as each new APQN