From: longpeng2--- via <qemu-devel@nongnu.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: "stefanha@redhat.com" <stefanha@redhat.com>,
"mst@redhat.com" <mst@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
Yechuan <yechuan@huawei.com>,
Huangzhichao <huangzhichao@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: RE: [RFC 06/10] vdpa-dev: implement the unrealize interface
Date: Thu, 6 Jan 2022 03:23:07 +0000 [thread overview]
Message-ID: <6e6f7fbb7db8498d985da9e50e65c324@huawei.com> (raw)
In-Reply-To: <20220105111612.epxi3w3ebsaye5mm@steredhat>
> -----Original Message-----
> From: Stefano Garzarella [mailto:sgarzare@redhat.com]
> Sent: Wednesday, January 5, 2022 7:16 PM
> To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
> <longpeng2@huawei.com>
> Cc: stefanha@redhat.com; mst@redhat.com; jasowang@redhat.com;
> cohuck@redhat.com; pbonzini@redhat.com; Gonglei (Arei)
> <arei.gonglei@huawei.com>; Yechuan <yechuan@huawei.com>; Huangzhichao
> <huangzhichao@huawei.com>; qemu-devel@nongnu.org
> Subject: Re: [RFC 06/10] vdpa-dev: implement the unrealize interface
>
> On Wed, Jan 05, 2022 at 08:58:56AM +0800, Longpeng(Mike) wrote:
> >From: Longpeng <longpeng2@huawei.com>
> >
> >Implements the .unrealize interface.
> >
> >Signed-off-by: Longpeng <longpeng2@huawei.com>
> >---
> > hw/virtio/vdpa-dev.c | 22 +++++++++++++++++++++-
> > 1 file changed, 21 insertions(+), 1 deletion(-)
> >
> >diff --git a/hw/virtio/vdpa-dev.c b/hw/virtio/vdpa-dev.c
> >index 2d534d837a..4e4dd3d201 100644
> >--- a/hw/virtio/vdpa-dev.c
> >+++ b/hw/virtio/vdpa-dev.c
> >@@ -133,9 +133,29 @@ out:
> > close(fd);
> > }
> >
> >+static void vhost_vdpa_vdev_unrealize(VhostVdpaDevice *s)
> >+{
> >+ VirtIODevice *vdev = VIRTIO_DEVICE(s);
> >+ int i;
> >+
> >+ for (i = 0; i < s->num_queues; i++) {
> ^
> `s->num_queues` seems uninitialized to me, maybe we could just remove
> the num_queues field from VhostVdpaDevice, and use `s->dev.nvqs` as in
> vhost_vdpa_device_realize().
>
Good catch, I'll fix the bug.
But I think we should keep the num_queues field, we need it if we support
migration in the next step, right?
> >+ virtio_delete_queue(s->virtqs[i]);
> >+ }
> >+ g_free(s->virtqs);
> >+ virtio_cleanup(vdev);
> >+
> >+ g_free(s->config);
> >+}
> >+
> > static void vhost_vdpa_device_unrealize(DeviceState *dev)
> > {
> >- return;
> >+ VirtIODevice *vdev = VIRTIO_DEVICE(dev);
> >+ VhostVdpaDevice *s = VHOST_VDPA_DEVICE(vdev);
> >+
> >+ virtio_set_status(vdev, 0);
> >+ vhost_dev_cleanup(&s->dev);
>
> If we will use `s->dev.nvqs` in vhost_vdpa_vdev_unrealize(), we should
> call vhost_dev_cleanup() after it, just before close() as we already do
> in the error path of vhost_vdpa_device_realize().
>
I'll try to fix the above bug first if you agree that we should keep the
num_queues field.
I just realize that I forgot to free s->dev.vqs here...
> >+ vhost_vdpa_vdev_unrealize(s);
> >+ close(s->vdpa.device_fd);
> > }
> >
> > static void
> >--
> >2.23.0
> >
next prev parent reply other threads:[~2022-01-06 3:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 0:58 [RFC 00/10] add generic vDPA device support Longpeng(Mike) via
2022-01-05 0:58 ` [RFC 01/10] virtio: get class_id and pci device id by the virtio id Longpeng(Mike) via
2022-01-05 4:37 ` Jason Wang
2022-01-05 5:47 ` longpeng2--- via
2022-01-05 6:15 ` Jason Wang
2022-01-10 3:03 ` longpeng2--- via
2022-01-05 10:46 ` Cornelia Huck
2022-01-06 1:50 ` longpeng2--- via
2022-01-10 5:43 ` Michael S. Tsirkin
2022-01-10 6:27 ` longpeng2--- via
2022-01-10 7:14 ` Michael S. Tsirkin
2022-01-05 0:58 ` [RFC 02/10] vhost: add 3 commands for vhost-vdpa Longpeng(Mike) via
2022-01-05 4:35 ` Jason Wang
2022-01-05 6:40 ` longpeng2--- via
2022-01-05 6:43 ` Jason Wang
2022-01-05 7:02 ` Michael S. Tsirkin
2022-01-05 7:54 ` Jason Wang
2022-01-05 8:37 ` longpeng2--- via
2022-01-05 9:09 ` Jason Wang
2022-01-05 12:26 ` Michael S. Tsirkin
2022-01-06 2:34 ` Jason Wang
2022-01-06 8:00 ` longpeng2--- via
2022-01-07 2:41 ` Jason Wang
2022-01-06 14:09 ` Michael S. Tsirkin
2022-01-07 2:53 ` Jason Wang
2022-01-05 9:12 ` Michael S. Tsirkin
2022-01-05 9:21 ` Jason Wang
2022-01-05 0:58 ` [RFC 03/10] vdpa: add the infrastructure of vdpa-dev Longpeng(Mike) via
2022-01-05 9:48 ` Stefan Hajnoczi
2022-01-06 1:22 ` longpeng2--- via
2022-01-06 11:25 ` Stefan Hajnoczi
2022-01-07 2:22 ` Jason Wang
2022-01-05 0:58 ` [RFC 04/10] vdpa-dev: implement the instance_init/class_init interface Longpeng(Mike) via
2022-01-05 10:00 ` Stefan Hajnoczi
2022-01-06 2:39 ` longpeng2--- via
2022-01-05 11:28 ` Stefano Garzarella
2022-01-06 2:40 ` longpeng2--- via
2022-01-05 0:58 ` [RFC 05/10] vdpa-dev: implement the realize interface Longpeng(Mike) via
2022-01-05 10:17 ` Stefan Hajnoczi
2022-01-06 3:02 ` longpeng2--- via
2022-01-06 11:34 ` Stefan Hajnoczi
2022-01-17 12:34 ` longpeng2--- via
2022-01-19 17:15 ` Stefan Hajnoczi
2022-01-05 0:58 ` [RFC 06/10] vdpa-dev: implement the unrealize interface Longpeng(Mike) via
2022-01-05 11:16 ` Stefano Garzarella
2022-01-06 3:23 ` longpeng2--- via [this message]
2022-01-10 9:38 ` Stefano Garzarella
2022-01-05 0:58 ` [RFC 07/10] vdpa-dev: implement the get_config/set_config interface Longpeng(Mike) via
2022-01-05 0:58 ` [RFC 08/10] vdpa-dev: implement the get_features interface Longpeng(Mike) via
2022-01-05 0:58 ` [RFC 09/10] vdpa-dev: implement the set_status interface Longpeng(Mike) via
2022-01-05 0:59 ` [RFC 10/10] vdpa-dev: mark the device as unmigratable Longpeng(Mike) via
2022-01-05 10:21 ` [RFC 00/10] add generic vDPA device support Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6e6f7fbb7db8498d985da9e50e65c324@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=arei.gonglei@huawei.com \
--cc=cohuck@redhat.com \
--cc=huangzhichao@huawei.com \
--cc=jasowang@redhat.com \
--cc=longpeng2@huawei.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=yechuan@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).