From: "Longpeng(Mike)" via <qemu-devel@nongnu.org>
To: <stefanha@redhat.com>, <mst@redhat.com>, <jasowang@redhat.com>,
<sgarzare@redhat.com>
Cc: <cohuck@redhat.com>, <pbonzini@redhat.com>,
<arei.gonglei@huawei.com>, <yechuan@huawei.com>,
<huangzhichao@huawei.com>, <qemu-devel@nongnu.org>,
<xiehong@huawei.com>, Longpeng <longpeng2@huawei.com>
Subject: [PATCH v9 4/5] vdpa-dev: mark the device as unmigratable
Date: Sat, 12 Nov 2022 22:40:12 +0800 [thread overview]
Message-ID: <20221112144013.1349-5-longpeng2@huawei.com> (raw)
In-Reply-To: <20221112144013.1349-1-longpeng2@huawei.com>
From: Longpeng <longpeng2@huawei.com>
The generic vDPA device doesn't support migration currently, so
mark it as unmigratable temporarily.
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Acked-by: Jason Wang <jasowang@redhat.com>
Signed-off-by: Longpeng <longpeng2@huawei.com>
---
hw/virtio/vdpa-dev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/virtio/vdpa-dev.c b/hw/virtio/vdpa-dev.c
index 2885d06cbe..62d83d3423 100644
--- a/hw/virtio/vdpa-dev.c
+++ b/hw/virtio/vdpa-dev.c
@@ -327,6 +327,7 @@ static Property vhost_vdpa_device_properties[] = {
static const VMStateDescription vmstate_vhost_vdpa_device = {
.name = "vhost-vdpa-device",
+ .unmigratable = 1,
.minimum_version_id = 1,
.version_id = 1,
.fields = (VMStateField[]) {
--
2.23.0
next prev parent reply other threads:[~2022-11-12 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 14:40 [PATCH v9 0/5] add generic vDPA device support Longpeng(Mike) via
2022-11-12 14:40 ` [PATCH v9 1/5] virtio: get class_id and pci device id by the virtio id Longpeng(Mike) via
2022-11-12 14:40 ` [PATCH v9 2/5] vdpa: add vdpa-dev support Longpeng(Mike) via
2022-11-12 14:40 ` [PATCH v9 3/5] vdpa: add vdpa-dev-pci support Longpeng(Mike) via
2022-11-12 14:40 ` Longpeng(Mike) via [this message]
2022-11-12 14:40 ` [PATCH v9 5/5] docs: Add generic vhost-vdpa device documentation Longpeng(Mike) via
2022-11-14 4:17 ` Jason Wang
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=20221112144013.1349-5-longpeng2@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=xiehong@huawei.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).