Lines Matching +full:default +full:- +full:on
7 ------------
14 On s390x, AP adapter cards are exposed via the AP bus. This document
19 -------------------------
28 on the machine model. Adapters assigned to the LPAR in which a linux host is
51 An AP queue is the means by which an AP command-request message is sent to an
57 which the AP command-request message is to be sent for processing.
63 * NQAP: to enqueue an AP command-request message to a queue
64 * DQAP: to dequeue an AP command-reply message from a queue
73 ----------------------------------------------
84 an APID from 0-255. If a bit is set, the corresponding adapter is valid for
89 corresponds to an AP queue index (APQI) from 0-255. If a bit is set, the
94 changed by an AP command-request message sent to a usage domain from the
96 0-255. If a bit is set, the corresponding domain can be modified by an AP
97 command-request message sent to a usage domain.
100 an APQN to identify the AP adapter and AP queue to which an AP command-request
102 command-reply message is to be received (DQAP instruction). The validity of an
109 The APQNs can provide secure key functionality - i.e., a private key is stored
110 on the adapter card for each of its domains - so each APQN must be assigned to
116 +----------+--------+--------+
120 +----------+--------+--------+
122 +----------+--------+--------+
132 +----------+--------+--------+
136 +----------+--------+--------+
138 +----------+--------+--------+
148 +----------+--------+--------+
152 +----------+--------+--------+
154 +----------+--------+--------+
159 AP Matrix Configuration on Linux Host
160 -------------------------------------
164 configured via its Activation Profile which can be edited on the HMC. When the
184 255 (0xff) are configured for the LPAR, the sysfs representation on the linux
200 A set of default device drivers are also created to control each type of AP
201 device that can be assigned to the LPAR on which a linux host is running::
220 range as 'usable by the default AP queue device drivers' or 'not usable by the
221 default device drivers' and thus available for use by the alternate device
227 The ``apmask`` is a 256-bit mask that identifies a set of AP adapter IDs
230 0-255. If a bit is set, the APID is marked as usable only by the default AP
234 The ``aqmask`` is a 256-bit mask that identifies a set of AP queue indexes
237 0-255. If a bit is set, the APQI is marked as usable only by the default AP
247 1, 2, 3, 4, 5, and 7-255 belong to the default drivers' pool, and 0 and 6
252 and APQIs marked as usable only by the default AP queue device drivers. If a
253 match is detected, only the default AP queue device drivers will be probed;
256 By default, the two masks are set to reserve all APQNs for use by the default
257 AP queue device drivers. There are two ways the default masks can be changed:
262 * An absolute hex string starting with 0x - like "0x12345678" - sets
264 with 0s on the right; for example, specifying a mask value of 0x41 is
276 * Individual bits in the mask can be switched on and off by specifying
278 number string must be prepended with a (``+``) or minus (``-``) to indicate
279 the corresponding bit is to be switched on (``+``) or off (``-``). Some
282 "+0" switches bit 0 on
283 "-13" switches bit 13 off
284 "+0x41" switches bit 65 on
285 "-0xff" switches bit 255 off
289 +0,-6,+0x47,-0xf0
291 Switches bits 0 and 71 (0x47) on
297 2. The masks can also be changed at boot time via parameters on the kernel
314 default drivers pool: adapter 0-15, domain 1
315 alternate drivers pool: adapter 16-255, domains 0, 2-255
320 The sysfs interfaces for configuring an AP matrix for a guest are built on the
331 ............ [vfio_ap-passthrough]
353 ............ [vfio_ap-passthrough]
366 ............ [vfio_ap-passthrough]
479 must be specified on the QEMU command line::
481 -device vfio_ap,sysfsdev=$path-to-mdev
489 /sys/devices/vfio_ap/matrix/mdev_supported_types/vfio_ap-passthrough/devices/$uuid
495 via the mediated matrix device's sysfs attribute files. Programs running on the
515 The AP facilities feature indicates that AP facilities are installed on the
517 are installed on the host system. The feature is s390-specific and is
518 represented as a parameter of the -cpu option on the QEMU command line::
520 qemu-system-s390x -cpu $model,ap=on|off
528 ``ap=on|off``
529 indicates whether AP facilities are installed (on) or not
530 (off). The default for CPU models zEC12 or newer
531 is ``ap=on``. AP facilities must be installed on the guest if a
532 vfio-ap device (``-device vfio-ap,sysfsdev=$path``) is configured
537 The QCI facility is used by the AP bus running on the guest to query the
539 only if the QCI facility is installed on the host system. The feature is
540 s390-specific and is represented as a parameter of the -cpu option on the
543 qemu-system-s390x -cpu $model,apqci=on|off
550 ``apqci=on|off``
551 indicates whether the QCI facility is installed (on) or
552 not (off). The default for CPU models zEC12 or newer
553 is ``apqci=on``; for older models, QCI will not be installed.
555 If QCI is installed (``apqci=on``) but AP facilities are not
563 running on the guest.
567 The APFT facility is used by the AP bus running on the guest to test the
569 only if the APFT facility is installed on the host system. The feature is
570 s390-specific and is represented as a parameter of the -cpu option on the
573 qemu-system-s390x -cpu $model,apft=on|off
581 ``apft=on|off``
582 indicates whether the APFT facility is installed (on) or
583 not (off). The default for CPU models zEC12 and
584 newer is ``apft=on`` for older models, APFT will not be
587 If APFT is installed (``apft=on``) but AP facilities are not
594 running on the guest will not detect CEX4 and newer devices
599 Hot plug a vfio-ap device into a running guest
602 Only one vfio-ap device can be attached to the virtual machine's ap-bus, so a
603 vfio-ap device can be hot plugged if and only if no vfio-ap device is attached
607 To hot plug a vfio-ap device, use the QEMU ``device_add`` command::
609 (qemu) device_add vfio-ap,sysfsdev="$path-to-mdev",id="$id"
611 Where the ``$path-to-mdev`` value specifies the absolute path to a mediated
615 Note that on Linux guests, the AP devices will be created in the
617 scan, so there may be a short delay before the AP devices are accessible on the
622 * A vfio-ap device has already been attached to the virtual machine's ap-bus.
627 Hot unplug a vfio-ap device from a running guest
630 A vfio-ap device can be unplugged from a running KVM guest if a vfio-ap device
631 has been attached to the virtual machine's ap-bus via the QEMU command line
634 To hot unplug a vfio-ap device, use the QEMU ``device_del`` command::
640 On a Linux guest, the AP devices will be removed from the ``/sys/bus/ap/devices``
641 directory on the guest when the AP bus subsequently performs its periodic scan,
645 The command will fail if the ``$path-to-mdev`` specified on the ``device_del`` command
646 does not match the value specified when the vfio-ap device was attached to
647 the virtual machine's ap-bus.
650 -----------------------------------------------------
654 three guests such that executing the lszcrypt command on the guests would
660 ------------------------------
661 05 CEX5C CCA-Coproc
662 05.0004 CEX5C CCA-Coproc
663 05.00ab CEX5C CCA-Coproc
666 06.00ab CEX5C CCA-Coproc
671 ------------------------------
679 ------------------------------
686 1. Install the vfio_ap module on the linux host. The dependency chain for the
710 -> Device Drivers
711 -> IOMMU Hardware Support
713 -> VFIO Non-Privileged userspace driver framework
714 -> Mediated device driver framework
715 -> VFIO driver for Mediated devices
716 -> I/O subsystem
717 -> VFIO support for AP devices
722 the corresponding APQNs must be removed from the default queue drivers pool
725 echo -5,-6 > /sys/bus/ap/apmask
727 echo -4,-0x47,-0xab,-0xff > /sys/bus/ap/aqmask
750 future, and for which there are few older systems on which to test.
768 ...... [vfio_ap-passthrough] (passthrough mediated matrix device type)
792 ...... [vfio_ap-passthrough]
865 …/usr/bin/qemu-system-s390x ... -cpu host,ap=on,apqci=on,apft=on -device vfio-ap,sysfsdev=/sys/devi…
869 …/usr/bin/qemu-system-s390x ... -cpu host,ap=on,apqci=on,apft=on -device vfio-ap,sysfsdev=/sys/devi…
873 …/usr/bin/qemu-system-s390x ... -cpu host,ap=on,apqci=on,apft=on -device vfio-ap,sysfsdev=/sys/devi…
881 ...... [vfio_ap-passthrough]
897 the pool of adapters and queues reserved for use by the default drivers.
900 -----------
903 to the default drivers pool of a queue that is still assigned to a mediated
910 mediated matrix device - see `Configuring an AP matrix for a linux guest`_
911 section above - while a running guest is using it is currently not supported.
914 is using AP devices, the vfio-ap device configured for the guest must be
915 unplugged before migrating the guest (see `Hot unplug a vfio-ap device from a