[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210819005258.790163dd.pasic@linux.ibm.com>
Date: Thu, 19 Aug 2021 00:52:58 +0200
From: Halil Pasic <pasic@...ux.ibm.com>
To: Christian Borntraeger <borntraeger@...ibm.com>
Cc: Alex Williamson <alex.williamson@...hat.com>,
Tony Krowiak <akrowiak@...ux.ibm.com>,
linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org,
cohuck@...hat.com, pasic@...ux.vnet.ibm.com, jjherne@...ux.ibm.com,
jgg@...dia.com, kwankhede@...dia.com, david@...hat.com,
pbonzini@...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
On Wed, 18 Aug 2021 18:50:47 +0200
Christian Borntraeger <borntraeger@...ibm.com> wrote:
> > that Halil's concern's around open/close races are addressed by Jason's
> > device_open/close series that's already in my next branch and he
> > provided an Ack, but there's still the above question regarding the
> > kvm->lock that was looking for a review from... I'm not sure, maybe
> > Connie or Paolo. Christian, is this specifically what you're ack'ing?
>
> My understanding was that Halil was ok in the end?
Yes, I'm OK with it provided it is merged after Jason's patch that makes
it a non-issue.
Regards,
Halil
Powered by blists - more mailing lists