From: Hanna Czenczek <hreitz@redhat.com>
To: qemu-devel@nongnu.org, virtio-fs@redhat.com
Cc: "Hanna Czenczek" <hreitz@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"German Maglione" <gmaglione@redhat.com>,
"Eugenio Pérez" <eperezma@redhat.com>
Subject: [PATCH v2 0/4] vhost-user: Back-end state migration
Date: Wed, 12 Jul 2023 13:16:58 +0200 [thread overview]
Message-ID: <20230712111703.28031-1-hreitz@redhat.com> (raw)
RFC:
https://lists.nongnu.org/archive/html/qemu-devel/2023-03/msg04263.html
v1:
https://lists.nongnu.org/archive/html/qemu-devel/2023-04/msg01575.html
Based-on: <20230711155230.64277-1-hreitz@redhat.com>
(“[PATCH 0/6] vhost-user: Add suspend/resume”)
https://lists.nongnu.org/archive/html/qemu-devel/2023-07/msg02450.html
Hi,
Most of the feedback on v1 focused on how to properly stop a device that
has internal state, both for the purpose of migration and just plainly
for VM stop/cont. I hope this is resolved by my vhost-user
suspend/resume series, which this series here is based on (linked
above).
Therefore, these patches here for the actual state transfer have changed
only little since v1:
- I’ve removed the original patch 1 that would explicitly re-enable all
vrings every time after using SET_FEATURES with
VHOST_USER_F_PROTOCOL_FEATURES, replacing it with the stand-alone
patch “[PATCH] vhost-user.rst: Clarify enabling/disabling vrings”
(20230712091704.15589-1-hreitz@redhat.com), which does not change
behavior but only documentation
- In its place, I’ve added a patch that adds documentation on the
protocol additions.
- Patch 2: Drastically shortened the commit message, this documentation
is now where it should be, namely in vhost-user.rst (added by patch
1). Also rebased on the “Add suspend/resume” series, which adds
feature bits and vhost-user operations of its own.
- Patch 3: Instead of checking dev->started to see that the device is
stopped, we might now want to check dev->suspended instead. However,
this is only set if the device actually supports suspending, so in
fact we cannot use it. Added documentation on this fact.
(Dropped checking enable_vqs, because this variable had been added
only by the old patch 1, which I dropped.)
Hanna Czenczek (4):
vhost-user.rst: Migrating back-end-internal state
vhost-user: Interface for migration state transfer
vhost: Add high-level state save/load functions
vhost-user-fs: Implement internal migration
docs/interop/vhost-user.rst | 87 +++++++++++
include/hw/virtio/vhost-backend.h | 24 +++
include/hw/virtio/vhost.h | 114 ++++++++++++++
hw/virtio/vhost-user-fs.c | 101 ++++++++++++-
hw/virtio/vhost-user.c | 147 ++++++++++++++++++
hw/virtio/vhost.c | 241 ++++++++++++++++++++++++++++++
6 files changed, 713 insertions(+), 1 deletion(-)
--
2.41.0
next reply other threads:[~2023-07-12 11:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 11:16 Hanna Czenczek [this message]
2023-07-12 11:16 ` [PATCH v2 1/4] vhost-user.rst: Migrating back-end-internal state Hanna Czenczek
2023-07-18 15:57 ` Stefan Hajnoczi
2023-07-19 16:33 ` Hanna Czenczek
2023-07-20 11:43 ` Stefan Hajnoczi
2023-07-18 16:12 ` Stefan Hajnoczi
2023-07-20 11:32 ` [Virtio-fs] " Hanna Czenczek
2023-07-12 11:17 ` [PATCH v2 2/4] vhost-user: Interface for migration state transfer Hanna Czenczek
2023-07-18 18:32 ` Stefan Hajnoczi
2023-07-20 12:13 ` [Virtio-fs] " Hao Xu
2023-07-20 13:20 ` Hanna Czenczek
2023-07-20 15:05 ` Hao Xu
2023-07-21 8:07 ` Hanna Czenczek
2023-07-21 8:23 ` Hao Xu
2023-07-12 11:17 ` [PATCH v2 3/4] vhost: Add high-level state save/load functions Hanna Czenczek
2023-07-18 18:42 ` Stefan Hajnoczi
2023-07-20 11:42 ` Hanna Czenczek
2023-07-21 15:18 ` Eugenio Perez Martin
2023-07-21 16:09 ` Hanna Czenczek
2023-07-12 11:17 ` [PATCH v2 4/4] vhost-user-fs: Implement internal migration Hanna Czenczek
2023-07-18 18:44 ` 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=20230712111703.28031-1-hreitz@redhat.com \
--to=hreitz@redhat.com \
--cc=eperezma@redhat.com \
--cc=gmaglione@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=virtio-fs@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).