arch/s390/vfio-ap.rst

150 be received (DQAP instruction). The validity of an APQN is defined by the matrix
190 1. AP matrix device
202    domains, and control domains comprising the matrix for a KVM guest.
205    by a KVM guest's SIE state description to grant the guest access to a matrix
222 	   |   +---------------->   Device core    +---------->  matrix device |
240   |      admin       |           | VFIO device core |--------->     matrix     |
252 2. The vfio-ap driver during its initialization will register a single 'matrix'
254    all vfio_ap mediated devices used to configure an AP matrix for a guest.
255 3. The /sys/devices/vfio_ap/matrix device is created by the device core
302    | | device  | |                        |  vfio_ap.ko  |<-> matrix
307 During initialization of the vfio_ap module, the matrix device is registered
310 matrix device.
327       /sys/devices/vfio_ap/matrix/mdev_supported_types/vfio_ap-passthrough
364     matrix:
385       vfio_ap mediated device's ap matrix masks to be replaced in one shot.
420     * Store the AP matrix configuration for the adapters, domains, and control
422     * Store the AP matrix configuration for the adapters, domains and control
435     VFIO_GROUP_NOTIFY_SET_KVM notifier callback function for the matrix mdev
437     VFIO iommu group for the matrix mdev device to the MDEV bus. Access to the
439     The KVM structure, is used to configure the guest's access to the AP matrix
444     matrix mdev device and deconfigures the guest's AP matrix.
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
778      /sys/devices/vfio_ap/matrix/
800      /sys/devices/vfio_ap/matrix/
808      --------------- matrix
817      --------------- matrix
826      --------------- matrix
837    This is how the matrix is configured for Guest1::
851    To display the matrix configuration for Guest1::
853 	 cat matrix
855    To display the matrix that is or will be assigned to Guest1::
859    This is how the matrix is configured for Guest2::
865    This is how the matrix is configured for Guest3::
933 	-device vfio-ap,sysfsdev=/sys/devices/vfio_ap/matrix/$uuid1 ...
938 	-device vfio-ap,sysfsdev=/sys/devices/vfio_ap/matrix/$uuid2 ...
943 	-device vfio-ap,sysfsdev=/sys/devices/vfio_ap/matrix/$uuid3 ...
949    /sys/devices/vfio_ap/matrix/
960 This will remove all of the matrix mdev device's sysfs structures including
961 the mdev device itself. To recreate and reconfigure the matrix mdev device,
1008 The features list can be found here: /sys/bus/matrix/devices/matrix/features
1014 cat /sys/bus/matrix/devices/matrix/features
1022 | guest_matrix | guest_matrix attribute exists. It reports the matrix of       |
1037 removed manually (i.e., echo 1 > /sys/devices/vfio_ap/matrix/$UUID/remove) while
1085 1. If the KVM guest was started with libvirt, you can hot plug a matrix mediated
1115       sysfsdev=/sys/devices/vfio_ap/matrix/62177883-f1bb-47f0-914d-32a22e3a8804,\
1128          sysfsdev=/sys/devices/vfio_ap/matrix/62177883-f1bb-47f0-914d-32a22e3a8804,\