[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210112185550.1ac49768.pasic@linux.ibm.com>
Date: Tue, 12 Jan 2021 18:55:50 +0100
From: Halil Pasic <pasic@...ux.ibm.com>
To: Tony Krowiak <akrowiak@...ux.ibm.com>
Cc: linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, 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, frankja@...ux.ibm.com, david@...hat.com,
hca@...ux.ibm.com, gor@...ux.ibm.com
Subject: Re: [PATCH v13 09/15] s390/vfio-ap: allow hot plug/unplug of AP
resources using mdev device
On Tue, 12 Jan 2021 02:12:51 +0100
Halil Pasic <pasic@...ux.ibm.com> wrote:
> > @@ -1347,8 +1437,11 @@ void vfio_ap_mdev_remove_queue(struct ap_device *apdev)
> > apqi = AP_QID_QUEUE(q->apqn);
> > vfio_ap_mdev_reset_queue(apid, apqi, 1);
> >
> > - if (q->matrix_mdev)
> > + if (q->matrix_mdev) {
> > + matrix_mdev = q->matrix_mdev;
> > vfio_ap_mdev_unlink_queue(q);
> > + vfio_ap_mdev_refresh_apcb(matrix_mdev);
> > + }
> >
> > kfree(q);
> > mutex_unlock(&matrix_dev->lock);
Shouldn't we first remove the queue from the APCB and then
reset? Sorry, I missed this one yesterday.
Regards,
Halil
Powered by blists - more mailing lists