From: Jason Wang <jasowang@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>, qemu-devel@nongnu.org
Cc: Cindy Lu <lulu@redhat.com>, Gautam Dawar <gdawar@xilinx.com>,
Cornelia Huck <cohuck@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
Zhu Lingshan <lingshan.zhu@intel.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Liuxiangdong <liuxiangdong5@huawei.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Eli Cohen <eli@mellanox.com>,
Harpreet Singh Anand <hanand@xilinx.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Parav Pandit <parav@mellanox.com>
Subject: Re: [PATCH v4 18/19] vdpa: Add device migration blocker
Date: Tue, 19 Jul 2022 10:36:56 +0800 [thread overview]
Message-ID: <2ea4381c-9868-98ab-c644-a93fefa014de@redhat.com> (raw)
In-Reply-To: <20220718102949.2868267-19-eperezma@redhat.com>
在 2022/7/18 18:29, Eugenio Pérez 写道:
> Since the vhost-vdpa device is exposing _F_LOG, adding a migration blocker if
> it uses CVQ.
>
> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
> ---
> include/hw/virtio/vhost-vdpa.h | 1 +
> hw/virtio/vhost-vdpa.c | 14 ++++++++++++++
> 2 files changed, 15 insertions(+)
>
> diff --git a/include/hw/virtio/vhost-vdpa.h b/include/hw/virtio/vhost-vdpa.h
> index 1111d85643..d10a89303e 100644
> --- a/include/hw/virtio/vhost-vdpa.h
> +++ b/include/hw/virtio/vhost-vdpa.h
> @@ -35,6 +35,7 @@ typedef struct vhost_vdpa {
> bool shadow_vqs_enabled;
> /* IOVA mapping used by the Shadow Virtqueue */
> VhostIOVATree *iova_tree;
> + Error *migration_blocker;
> GPtrArray *shadow_vqs;
> const VhostShadowVirtqueueOps *shadow_vq_ops;
> void *shadow_vq_ops_opaque;
> diff --git a/hw/virtio/vhost-vdpa.c b/hw/virtio/vhost-vdpa.c
> index beaaa7049a..795ed5a049 100644
> --- a/hw/virtio/vhost-vdpa.c
> +++ b/hw/virtio/vhost-vdpa.c
> @@ -20,6 +20,7 @@
> #include "hw/virtio/vhost-shadow-virtqueue.h"
> #include "hw/virtio/vhost-vdpa.h"
> #include "exec/address-spaces.h"
> +#include "migration/blocker.h"
> #include "qemu/cutils.h"
> #include "qemu/main-loop.h"
> #include "cpu.h"
> @@ -1022,6 +1023,13 @@ static bool vhost_vdpa_svqs_start(struct vhost_dev *dev)
> return true;
> }
>
> + if (v->migration_blocker) {
> + int r = migrate_add_blocker(v->migration_blocker, &err);
> + if (unlikely(r < 0)) {
> + goto err_migration_blocker;
> + }
> + }
> +
> for (i = 0; i < v->shadow_vqs->len; ++i) {
> VirtQueue *vq = virtio_get_queue(dev->vdev, dev->vq_index + i);
> VhostShadowVirtqueue *svq = g_ptr_array_index(v->shadow_vqs, i);
> @@ -1064,6 +1072,9 @@ err:
> vhost_svq_stop(svq);
> }
>
> +err_migration_blocker:
> + error_reportf_err(err, "Cannot setup SVQ %u: ", i);
So I got this:
FAILED: libqemu-x86_64-softmmu.fa.p/hw_virtio_vhost-vdpa.c.o
cc -m64 -mcx16 -Ilibqemu-x86_64-softmmu.fa.p -I. -I.. -Itarget/i386
-I../target/i386 -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/pixman-1
-I/usr/include/capstone -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fdiagnostics-color=auto
-Wall -Winvalid-pch -Werror -std=gnu11 -O2 -g -isystem
/home/devel/git/qemu/linux-headers -isystem linux-headers -iquote .
-iquote /home/devel/git/qemu -iquote /home/devel/git/qemu/include
-iquote /home/devel/git/qemu/tcg/i386 -pthread -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wundef
-Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common
-fwrapv -Wold-style-declaration -Wold-style-definition -Wtype-limits
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers
-Wempty-body -Wnested-externs -Wendif-labels -Wexpansion-to-defined
-Wimplicit-fallthrough=2 -Wno-missing-include-dirs
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -fPIE
-isystem../linux-headers -isystemlinux-headers -DNEED_CPU_H
'-DCONFIG_TARGET="x86_64-softmmu-config-target.h"'
'-DCONFIG_DEVICES="x86_64-softmmu-config-devices.h"' -MD -MQ
libqemu-x86_64-softmmu.fa.p/hw_virtio_vhost-vdpa.c.o -MF
libqemu-x86_64-softmmu.fa.p/hw_virtio_vhost-vdpa.c.o.d -o
libqemu-x86_64-softmmu.fa.p/hw_virtio_vhost-vdpa.c.o -c
../hw/virtio/vhost-vdpa.c
../hw/virtio/vhost-vdpa.c: In function ‘vhost_vdpa_dev_start’:
../hw/virtio/vhost-vdpa.c:1076:5: error: ‘i’ may be used uninitialized
in this function [-Werror=maybe-uninitialized]
1076 | error_reportf_err(err, "Cannot setup SVQ %u: ", i);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../hw/virtio/vhost-vdpa.c:1020:14: note: ‘i’ was declared here
1020 | unsigned i;
| ^
cc1: all warnings being treated as errors
And this error is kind of duplicated with the one that is reported in
label "err" above.
Thanks
> +
> return false;
> }
>
> @@ -1083,6 +1094,9 @@ static bool vhost_vdpa_svqs_stop(struct vhost_dev *dev)
> }
> }
>
> + if (v->migration_blocker) {
> + migrate_del_blocker(v->migration_blocker);
> + }
> return true;
> }
>
next prev parent reply other threads:[~2022-07-19 2:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 10:29 [PATCH v4 00/19] vdpa net devices Rx filter change notification with Shadow VQ Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 01/19] vhost: move descriptor translation to vhost_svq_vring_write_descs Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 02/19] virtio-net: Expose MAC_TABLE_ENTRIES Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 03/19] virtio-net: Expose ctrl virtqueue logic Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 04/19] vhost: Reorder vhost_svq_kick Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 05/19] vhost: Move vhost_svq_kick call to vhost_svq_add Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 06/19] vhost: Check for queue full at vhost_svq_add Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 07/19] vhost: Decouple vhost_svq_add from VirtQueueElement Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 08/19] vhost: Add SVQDescState Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 09/19] vhost: Track number of descs in SVQDescState Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 10/19] vhost: add vhost_svq_push_elem Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 11/19] vhost: Expose vhost_svq_add Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 12/19] vhost: add vhost_svq_poll Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 13/19] vhost: Add svq avail_handler callback Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 14/19] vdpa: Export vhost_vdpa_dma_map and unmap calls Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 15/19] vdpa: manual forward CVQ buffers Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 16/19] vdpa: Buffer CVQ support on shadow virtqueue Eugenio Pérez
2022-07-19 2:39 ` Jason Wang
2022-07-19 5:42 ` Eugenio Perez Martin
2022-07-19 6:45 ` Eugenio Perez Martin
2022-07-18 10:29 ` [PATCH v4 17/19] vdpa: Extract get features part from vhost_vdpa_get_max_queue_pairs Eugenio Pérez
2022-07-18 10:29 ` [PATCH v4 18/19] vdpa: Add device migration blocker Eugenio Pérez
2022-07-19 2:36 ` Jason Wang [this message]
2022-07-18 10:29 ` [PATCH v4 19/19] vdpa: Add x-svq to NetdevVhostVDPAOptions Eugenio Pérez
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=2ea4381c-9868-98ab-c644-a93fefa014de@redhat.com \
--to=jasowang@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=cohuck@redhat.com \
--cc=eblake@redhat.com \
--cc=eli@mellanox.com \
--cc=eperezma@redhat.com \
--cc=gdawar@xilinx.com \
--cc=hanand@xilinx.com \
--cc=lingshan.zhu@intel.com \
--cc=liuxiangdong5@huawei.com \
--cc=lulu@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=parav@mellanox.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.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).