From: Hanna Czenczek <hreitz@redhat.com>
To: qemu-devel@nongnu.org, virtio-fs@redhat.com
Cc: "Hanna Czenczek" <hreitz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"German Maglione" <gmaglione@redhat.com>
Subject: [Virtio-fs] [PATCH v3 0/5] vhost-user: Back-end state migration
Date: Fri, 15 Sep 2023 12:25:25 +0200 [thread overview]
Message-ID: <20230915102531.55894-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
v2:
https://lists.nongnu.org/archive/html/qemu-devel/2023-07/msg02604.html
Hi,
I’ve decided not to work on vhost-user SUSPEND/RESUME for now – it is
not technically required for virtio-fs migration, which is the actual
priority for me now. While we do want to have SUSPEND/RESUME at some
point, the only practically existing reason for it is to be able to
implement vhost-level resetting in virtiofsd, but that is not related to
migration.
So one of the changes in v3 is that it no longer depends on the
vhost-user SUSPEND/RESUME series, and describes the migration protocol
without the device being suspended at any point, but merely that the
vrings are stopped.
Other changes include:
- Patch 1:
- Rephrased a lot
- Added a description for the VHOST_USER_SET_DEVICE_STATE_FD
parameters
- Renamed VHOST_USER_PROTOCOL_F_MIGRATORY_STATE to
VHOST_USER_PROTOCOL_F_DEVICE_STATE
- enum variants changed in value due to dropping the SUSPEND/RESUME
dependency
- Patch 2:
- Pulled in, was a stand-alone patch before
- Dropped a sentence about ring state before feature negotiations, as
the rings are not to be used during that period anyway
- Bit of rephrasing
- Patch 3:
- Renamed “migratory state” to “device state”
- enum variants changed in value due to dropping the SUSPEND/RESUME
dependency
- Patch 4:
- Changed `f` to @f (referencing parameter “f”) in comments
- Use g_autofree for the transfer buffer
- Note SUSPEND state as a future feature, not currently existing
- Wrap read() and write() in RETRY_ON_EINTR()
- Patch 5:
- Renamed “migratory state” to “device state”
- (kept R-b still)
Hanna Czenczek (5):
vhost-user.rst: Migrating back-end-internal state
vhost-user.rst: Clarify enabling/disabling vrings
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 | 188 ++++++++++++++++++++++-
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 | 148 ++++++++++++++++++
hw/virtio/vhost.c | 241 ++++++++++++++++++++++++++++++
6 files changed, 810 insertions(+), 6 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-15 10:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 10:25 Hanna Czenczek [this message]
2023-09-15 10:25 ` [Virtio-fs] [PATCH v3 1/5] vhost-user.rst: Migrating back-end-internal state Hanna Czenczek
2023-09-25 19:04 ` Stefan Hajnoczi
2023-09-15 10:25 ` [Virtio-fs] [PATCH v3 2/5] vhost-user.rst: Clarify enabling/disabling vrings Hanna Czenczek
2023-09-25 19:15 ` Stefan Hajnoczi
2023-09-26 13:54 ` Hanna Czenczek
2023-09-26 19:30 ` Stefan Hajnoczi
2023-09-15 10:25 ` [Virtio-fs] [PATCH v3 3/5] vhost-user: Interface for migration state transfer Hanna Czenczek
2023-09-25 20:18 ` Stefan Hajnoczi
2023-09-15 10:25 ` [Virtio-fs] [PATCH v3 4/5] vhost: Add high-level state save/load functions Hanna Czenczek
2023-09-25 20:23 ` Stefan Hajnoczi
2023-09-15 10:25 ` [Virtio-fs] [PATCH v3 5/5] vhost-user-fs: Implement internal migration Hanna Czenczek
2023-09-25 20:26 ` Stefan Hajnoczi
2023-09-25 20:48 ` [Virtio-fs] [PATCH v3 0/5] vhost-user: Back-end state migration Stefan Hajnoczi
2023-09-26 13:32 ` Hanna Czenczek
2023-09-26 19:20 ` Stefan Hajnoczi
2023-09-26 20:10 ` Stefan Hajnoczi
2023-09-27 8:32 ` Hanna Czenczek
2023-09-27 20:19 ` Stefan Hajnoczi
2023-09-27 8:13 ` Hanna Czenczek
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=20230915102531.55894-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 read-only IMAP folder(s) and NNTP newsgroup(s).