[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3f45fe31-6666-ac87-3a98-dd942b5dfb3c@linux.ibm.com>
Date: Mon, 2 Aug 2021 09:10:26 -0400
From: Tony Krowiak <akrowiak@...ux.ibm.com>
To: linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: borntraeger@...ibm.com, cohuck@...hat.com,
pasic@...ux.vnet.ibm.com, jjherne@...ux.ibm.com, jgg@...dia.com,
alex.williamson@...hat.com, kwankhede@...dia.com, david@...hat.com,
pbonzini@...hat.com, david@...hat.com, frankja@...ux.ibm.com,
imbrenda@...ux.ibm.com
Subject: Re: [PATCH 0/2] s390/vfio-ap: do not open code locks for
VFIO_GROUP_NOTIFY_SET_KVM notification
PING!
This patch will pre-req version 17 of a patch series I have waiting in
the wings,
so I'd like to get this one merged ASAP. In particular, if a KVM
maintainer can
take a look at the comments concerning the taking of the kvm->lock
before the
matrix_mdev->lock it would be greatly appreciated. Those comments begin with
Message ID <20210727004329.3bcc7d4f.pasic@...ux.ibm.com> from Halil Pasic.
On 7/19/21 3:35 PM, Tony Krowiak wrote:
> This series is actually only comprised of a single patch to replace the
> open coded locks used during VFIO_GROUP_NOTIFY_SET_KVM notification. The
> first patch is included because it is a pre-req slotted to be merged but is
> not yet available in the kernel.
>
> Tony Krowiak (2):
> s390/vfio-ap: r/w lock for PQAP interception handler function pointer
> s390/vfio-ap: replace open coded locks for VFIO_GROUP_NOTIFY_SET_KVM
> notification
>
> arch/s390/include/asm/kvm_host.h | 8 +-
> arch/s390/kvm/kvm-s390.c | 28 +++++-
> arch/s390/kvm/priv.c | 10 +-
> drivers/s390/crypto/vfio_ap_ops.c | 127 +++++++++-----------------
> drivers/s390/crypto/vfio_ap_private.h | 4 +-
> 5 files changed, 77 insertions(+), 100 deletions(-)
>
Powered by blists - more mailing lists