On 10/08/2018 11:14, Cornelia Huck wrote:
On Wed, 8 Aug 2018 10:44:27 -0400
Tony Krowiak <akrow...@linux.vnet.ibm.com> wrote:
From: Tony Krowiak <akrow...@linux.ibm.com>
Let's call PAPQ(ZAPQ) to zeroize a queue:
* For each queue configured for a mediated matrix device
when it is released.
Zeroizing a queue resets the queue, clears all pending
messages for the queue entries and disables adapter interruptions
associated with the queue.
Signed-off-by: Tony Krowiak <akrow...@linux.ibm.com>
Reviewed-by: Halil Pasic <pa...@linux.ibm.com>
Tested-by: Michael Mueller <m...@linux.ibm.com>
Tested-by: Farhan Ali <al...@linux.ibm.com>
Signed-off-by: Christian Borntraeger <borntrae...@de.ibm.com>
drivers/s390/crypto/vfio_ap_ops.c | 29 ++++++++++++++++++++++++++++-
drivers/s390/crypto/vfio_ap_private.h | 25 +++++++++++++++++++++++++
2 files changed, 53 insertions(+), 1 deletions(-)
@@ -788,7 +812,10 @@ static void vfio_ap_mdev_release(struct mdev_device *mdev)
struct ap_matrix_mdev *matrix_mdev = mdev_get_drvdata(mdev);
+ if (matrix_mdev->kvm)
Confused. Why is the check for matrix_mdev->kvm added here?
When using the KVM notifier we can get two notifications:
-> KVM is here / is comming
-> KVM is not here / disappearing
In the first case we initialize matrix_mdev->kvm with a pointer to KVM
In the second case we nullify the pointer.
During the open of the mediated device, the guest should have been started
or we refuse to start.
During the close of the mediated device, the guest should be there, but
we have no certitude that the guest did not disappear before the VFIO
file being closed.
Since we do not allow multiple guests using the same mediated device
this case should not happen with QEMU. But I am not sure that
a rogue user program could not stop KVM before closing the VFIO
Maybe Alex can confirm this point, if not we can remove the test.
+ vfio_ap_mdev_reset_queues(mdev, true);
matrix_mdev->kvm = NULL;
Linux/KVM/QEMU in Böblingen - Germany