arch/s390/vfio-ap.rst

14 is to make AP cards available to KVM guests using the VFIO mediated device
128 control domains assigned to the KVM guest:
131   to the KVM guest. Each bit in the mask, from left to right, corresponds to
133   use by the KVM guest.
136   assigned to the KVM guest. Each bit in the mask, from left to right,
138   corresponding queue is valid for use by the KVM guest.
141   assigned to the KVM guest. The ADM bit mask controls which domains can be
198 1. Provides the interfaces to secure APQNs for exclusive use of KVM guests.
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
208 Reserve APQNs for exclusive use of KVM guests
249 The process for reserving an AP queue for use by a KVM guest is:
371       fields respectively of the KVM guest's CRYCB. This may differ from the
389     * Store the reference to the KVM structure for the guest using the mdev
408     KVM structure used to configure the KVM guest is provided via this callback.
409     The KVM structure, is used to configure the guest's access to the AP matrix
422 Configuring the AP resources for a KVM guest will be performed when the
424 function is called when userspace connects to KVM. The guest's AP resources are
434 The linux device model precludes passing a device through to a KVM guest that
437 driver will not be assigned to a KVM guest's matrix. The AP architecture,
459 facility. These features/facilities are made available to a KVM guest via the
463    feature will be enabled by KVM only if the AP instructions are installed
499 Let's now provide an example to illustrate how KVM guests may be given
547    * KVM
555    * KVM
942 An adapter, domain or control domain may be hot plugged into a running KVM
958 An adapter, domain or control domain may be hot unplugged from a running KVM
962 Over-provisioning of AP queues for a KVM guest:
967 available, it will be automatically hot-plugged into the KVM guest using
975 intervention by a system administrator. Before a KVM guest can be migrated,
978 the mdev is in use by a KVM guest. If the guest is being emulated by QEMU,
981 1. If the KVM guest was started with libvirt, you can hot unplug the mdev via
1021 After live migration of the KVM guest completes, an AP configuration can be
1022 restored to the KVM guest by hot plugging a vfio_ap mediated device on the target
1025 1. If the KVM guest was started with libvirt, you can hot plug a matrix mediated