[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b45cb3cc-1b04-4476-ebbd-7b12aecc31e4@linux.ibm.com>
Date: Wed, 19 May 2021 07:52:33 -0400
From: Tony Krowiak <akrowiak@...ux.ibm.com>
To: Halil Pasic <pasic@...ux.ibm.com>
Cc: linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, jjherne@...ux.ibm.com, freude@...ux.ibm.com,
borntraeger@...ibm.com, cohuck@...hat.com, mjrosato@...ux.ibm.com,
alex.williamson@...hat.com, kwankhede@...dia.com,
fiuczy@...ux.ibm.com
Subject: Re: [PATCH v16 00/14] s390/vfio-ap: dynamic configuration support
On 5/18/21 12:54 PM, Halil Pasic wrote:
> On Tue, 18 May 2021 09:26:01 -0400
> Tony Krowiak <akrowiak@...ux.ibm.com> wrote:
>
>> Ping!
> I'm already working on it. I went trough the all the changes once, and
> I'm currently trying to understand the new usages of
> matrix_mdev->wait_for_kvm and matrix_mdev->kvm_busy. You seem to be
> using these a new purpose...
I merely added that to the commit function which sets the masks
in the guest's APCB. This is the same usage as in the
vfio_ap_mdev_unset_kvm() function, to prevent a lockdep splat
similar to the scenario for which those fields were added in the
first place.
>
> Regards,
> Halil
Powered by blists - more mailing lists