Lines Matching full:matrix
153 be received (DQAP instruction). The validity of an APQN is defined by the matrix
193 1. AP matrix device
195 3. VFIO AP mediated matrix pass-through device
203 2. Sets up the VFIO mediated device interfaces to manage a mediated matrix
205 domains, and control domains comprising the matrix for a KVM guest.
208 SIE state description to grant the guest access to a matrix of AP devices
224 | +----------------> Device core +----------> matrix device |
242 | admin | | VFIO device core |---------> matrix |
254 2. The vfio-ap driver during its initialization will register a single 'matrix'
256 all mediated matrix devices used to configure an AP matrix for a guest.
257 3. The /sys/devices/vfio_ap/matrix device is created by the device core
272 9. The administrator creates a passthrough type mediated matrix device to be
282 * Register an AP mediated bus driver to add a mediated matrix device to and
284 * Create and destroy a mediated matrix device
285 * Add a mediated matrix device to and remove it from the AP mediated bus driver
286 * Add a mediated matrix device to and remove it from an IOMMU group
289 of the VFIO AP mediated matrix device driver::
304 | | device | | | vfio_ap.ko |<-> matrix
309 During initialization of the vfio_ap module, the matrix device is registered
312 matrix device.
329 /sys/devices/vfio_ap/matrix/mdev_supported_types/vfio_ap-passthrough
346 the number of mediated matrix passthrough devices
354 structure will be created in the mediated matrix device's directory. The
355 sysfs attributes for a mediated matrix device are:
359 mediated matrix device. To assign/unassign an adapter, the APID of the
363 the mediated matrix device. To assign/unassign a domain, the domain
366 matrix:
368 of the adapter and domain numbers assigned to the mediated matrix device.
371 to/from the mediated matrix device. To assign/unassign a control domain,
376 mediated matrix device.
384 * Store the AP matrix configuration for the adapters, domains, and control
388 deallocates the mediated matrix device's ap_matrix_mdev structure. This will
395 VFIO_GROUP_NOTIFY_SET_KVM notifier callback function for the mdev matrix
397 for the mdev matrix device to the MDEV bus. Access to the KVM structure used
399 is used to configure the guest's access to the AP matrix defined via the
400 mediated matrix device's sysfs attribute files.
403 mdev matrix device and deconfigures the guest's AP matrix.
407 Configuring the AP matrix for a KVM guest will be performed when the
409 function is called when QEMU connects to KVM. The guest's AP matrix is
413 mediated matrix device via its 'assign_adapter' interface.
415 mediated matrix device via its 'assign_domain' interface.
417 mediated matrix device via its 'assign_control_domains' interface.
685 /sys/devices/vfio_ap/matrix/
687 ------ [vfio_ap-passthrough] (passthrough mediated matrix device type)
707 /sys/devices/vfio_ap/matrix/
715 --------------- matrix
724 --------------- matrix
733 --------------- matrix
741 This is how the matrix is configured for Guest1::
755 To display the matrix configuration for Guest1::
757 cat matrix
759 This is how the matrix is configured for Guest2::
765 This is how the matrix is configured for Guest3::
786 previously assigned domains can be assigned to another mediated matrix
787 device. If an APQN is assigned to another mediated matrix device, the
805 previously assigned adapters can be assigned to another mediated matrix
806 device. If an APQN is assigned to another mediated matrix device, the
817 -device vfio-ap,sysfsdev=/sys/devices/vfio_ap/matrix/$uuid1 ...
822 -device vfio-ap,sysfsdev=/sys/devices/vfio_ap/matrix/$uuid2 ...
827 -device vfio-ap,sysfsdev=/sys/devices/vfio_ap/matrix/$uuid3 ...
829 When the guest is shut down, the mediated matrix devices may be removed.
831 Using our example again, to remove the mediated matrix device $uuid1::
833 /sys/devices/vfio_ap/matrix/
844 This will remove all of the mdev matrix device's sysfs structures including
845 the mdev device itself. To recreate and reconfigure the mdev matrix device,
849 It is not necessary to remove an mdev matrix device, but one may want to
851 host. If the mdev matrix device is removed, one may want to also reconfigure
863 * Dynamically modifying the AP matrix for a running guest (which would amount to