[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACGkMEs7f63SDxed0qg4XVspJ9cSCTRrV8R-MUUVQCvjAXp+DA@mail.gmail.com>
Date: Thu, 19 May 2022 16:08:22 +0800
From: Jason Wang <jasowang@...hat.com>
To: Cornelia Huck <cohuck@...hat.com>
Cc: mst <mst@...hat.com>,
virtualization <virtualization@...ts.linux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
"Paul E. McKenney" <paulmck@...nel.org>,
Marc Zyngier <maz@...nel.org>,
Halil Pasic <pasic@...ux.ibm.com>,
eperezma <eperezma@...hat.com>, Cindy Lu <lulu@...hat.com>,
Stefano Garzarella <sgarzare@...hat.com>,
Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
Vineeth Vijayan <vneethv@...ux.ibm.com>,
Peter Oberparleiter <oberpar@...ux.ibm.com>,
linux-s390@...r.kernel.org
Subject: Re: [PATCH V5 7/9] virtio: allow to unbreak virtqueue
On Wed, May 18, 2022 at 6:04 PM Cornelia Huck <cohuck@...hat.com> wrote:
>
> On Wed, May 18 2022, Jason Wang <jasowang@...hat.com> wrote:
>
> > This patch allows the new introduced __virtio_break_device() to
> > unbreak the virtqueue.
> >
> > Cc: Thomas Gleixner <tglx@...utronix.de>
> > Cc: Peter Zijlstra <peterz@...radead.org>
> > Cc: "Paul E. McKenney" <paulmck@...nel.org>
> > Cc: Marc Zyngier <maz@...nel.org>
> > Cc: Halil Pasic <pasic@...ux.ibm.com>
> > Cc: Cornelia Huck <cohuck@...hat.com>
> > Cc: Vineeth Vijayan <vneethv@...ux.ibm.com>
> > Cc: Peter Oberparleiter <oberpar@...ux.ibm.com>
> > Cc: linux-s390@...r.kernel.org
> > Signed-off-by: Jason Wang <jasowang@...hat.com>
> > ---
> > drivers/virtio/virtio_ring.c | 21 +++++++++++++++++++++
> > include/linux/virtio.h | 1 +
> > 2 files changed, 22 insertions(+)
> >
> > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
> > index cfb028ca238e..5b7df7c455f0 100644
> > --- a/drivers/virtio/virtio_ring.c
> > +++ b/drivers/virtio/virtio_ring.c
> > @@ -2397,6 +2397,27 @@ void virtio_break_device(struct virtio_device *dev)
> > }
> > EXPORT_SYMBOL_GPL(virtio_break_device);
> >
> > +/*
> > + * This should allow the device to be used by the driver. You may
> > + * need to grab appropriate locks to flush. This should only be used
>
> Hm, to flush what?
How about "to flush the write to vq->broken"?
>
> > + * in some specific case e.g (probing and restoring). Driver should
> > + * not call this directly.
>
> Maybe "This function should only be called by the core, not directly by
> the driver."?
Ok.
Thanks
>
> > + */
> > +void __virtio_unbreak_device(struct virtio_device *dev)
> > +{
> > + struct virtqueue *_vq;
> > +
> > + spin_lock(&dev->vqs_list_lock);
> > + list_for_each_entry(_vq, &dev->vqs, list) {
> > + struct vring_virtqueue *vq = to_vvq(_vq);
> > +
> > + /* Pairs with READ_ONCE() in virtqueue_is_broken(). */
> > + WRITE_ONCE(vq->broken, false);
> > + }
> > + spin_unlock(&dev->vqs_list_lock);
> > +}
> > +EXPORT_SYMBOL_GPL(__virtio_unbreak_device);
> > +
> > dma_addr_t virtqueue_get_desc_addr(struct virtqueue *_vq)
> > {
> > struct vring_virtqueue *vq = to_vvq(_vq);
>
Powered by blists - more mailing lists