This patch implement PQAP/AQIC interception in KVM. To implement this we need to add a new structure, vfio_ap_queue,to be able to retrieve the mediated device associated with a queue and specific values needed to register/unregister the interrupt structures: - APQN: to be able to issue the commands and search for queue structures - NIB : to unpin the NIB on clear IRQ - ISC : to unregister with the GIB interface - MATRIX: a pointer to the matrix mediated device - LIST: the list_head to handle the vfio_queue life cycle Having this structure and the list management greatly ease the handling of the AP queues and diminues the LOCs needed in the vfio_ap driver by more than 150 lines in comparison with the previous version. 0) Queues life cycle vfio_ap_queues are created on probe We define one bucket on the matrix device to store the free vfio_ap_queues, the queues not assign to any matrix mediated device. We define one bucket on each matrix mediated device to hold the vfio_ap_queues belonging to it. vfio_ap_queues are deleted on remove This makes the search for a queue easy and the detection of assignent incoherency obvious (the queue is not avilable) and simplifies assignment. 1) Phase 1, probe and remove from vfio_ap_queue The vfio_ap_queue structures are dynamically allocated and setup when a queue is probed by the ap_vfio_driver. The vfio_ap_queue is linked to the ap_queue device as the driver data. The new The vfio_ap_queue is put on a free_list belonging to the matrix device. The vfio_ap_queue are free during remove. 2) Phase 2, assignment of vfio_ap_queue to a mediated device When a APID is assigned we look for APQI already assigned to the matrix mediated device and associate all the queue with the APQN = (APID,APQI) to the mediated device by adding them to the mediated device queue list. We do the same when a APQI is assigned. If any queue with a matching APQN can not be found on the matrix device free list it means it is already associated to another matrix mediated device and no queue is added to the matrix mediated device. 3) Phase 3, starting the guest When the VFIO device is opened the PQAP callback and a pointer to the matrix mediated device are set inside KVM during the open callback. When the device is closed or if a queue is removed, the vfio_ap_queue is dissociated from the mediated device. 4) Phase 3 intercepting the PQAP/AQIC instruction On interception of the PQAP/AQIC instruction, the interception code makes sure the pqap_hook is initialized and allowed to be called and call it. Otherwise it reports the usual -EOPNOTSUPP return code to let QEMU handle the fault. the pqap callback search for the queue asociated with the APQN stored in the register 0, setting the code to "illegal APQN" if the vfio_ap_queue can not be found. Depending on the "i" bit of the register 1, the pqap callback setup or clear the interruption by calling the host format PQAP/AQIC instruction. When seting up the interruption it uses the NIB and the guest ISC provided by the guest and the host ISC provided by the registration to the GIB code, pin the NIB and also stores ISC and NIB inside the vfio_ap_queue structure. When clearing the interrupt it retrieves the host ISC to unregister with the GIB code and unpin the NIB. We take care when enabling GISA that the guest may have issued a reset and will not need to disable the interuptions before re-enabling interruptions. To make sure that the module holding the callback does not disapear we use a module reference counting in the structure containing the callback. 5) Phase 4 clean dissociation from the mediated device on remove On removing of the AP device the remove callback is called. To be sure that the guest will not access the queue anymore we clear the APID CRYCB bit. Cleaning the APID, over the APQI, is chosen because the architecture specifies that only the APID can be dynamically changed outside IPL. To be sure that the IRQ is cleared before the GISA is free we use the KVM reference counting, raise it in open, lower it on release. 6) Associated QEMU patch There is a QEMU patch which is needed to enable the PQAP/AQIC facility in the guest. Posted in qemu-devel@xxxxxxxxxx as: Message-Id: <1550146494-21085-1-git-send-email-pmorel@xxxxxxxxxxxxx> Pierre Morel (7): s390: ap: kvm: add PQAP interception for AQIC s390: ap: new vfio_ap_queue structure vfio: ap: register IOMMU VFIO notifier s390: ap: setup relation betwen KVM and mediated device s390: ap: implement PAPQ AQIC interception in kernel s390: ap: Cleanup on removing the AP device s390: ap: kvm: Enable PQAP/AQIC facility for the guest arch/s390/include/asm/kvm_host.h | 8 + arch/s390/kvm/priv.c | 62 +++ arch/s390/tools/gen_facilities.c | 1 + drivers/s390/crypto/ap_bus.h | 1 + drivers/s390/crypto/vfio_ap_drv.c | 69 +++- drivers/s390/crypto/vfio_ap_ops.c | 727 +++++++++++++++++++++++----------- drivers/s390/crypto/vfio_ap_private.h | 20 + 7 files changed, 658 insertions(+), 230 deletions(-) -- 2.7.4 Changelog from v4: - Add forgotten locking for vfio_get_queue() in pqap callback (Conny / Halil) - Add KVM reference counting to make sure GISA is free after IRQ (Christian / Halil) - Take care that ISC = 0 is a valid ISC (Halil) - Integrate the PQAP call back in a structure with module owner reference counting to make sure the callback does not disappear. - Restrict functionality to always open KVM before opening the VFIO device. - Search all devices in the vfio_ap driver list when associating a queue to a mediated device (Halil / Tony) - Get vfio_ap_free_irq() out of vfio_ap_mdev_reset_queue() to call it always, whatever the result of the reset. (Tony) Changelog from v3: - Associating the vfio_queues during APID/APQI assign (Tony) - Dissociating the vfio_queues during APID/APQI unassign (Tony) - Taking care that the guest can directly disable the interrupt by using a RESET (Halil) - Remove the patch creating the matrix bus to accelerate its integration in Linux stable (Christian)
