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>,
"Anton Kuchin" <antonkuchin@yandex-team.ru>
Subject: [Virtio-fs] [PATCH v5 0/7] vhost-user: Back-end state migration
Date: Mon, 16 Oct 2023 15:42:36 +0200 [thread overview]
Message-ID: <20231016134243.68248-1-hreitz@redhat.com> (raw)
v2:
https://lists.nongnu.org/archive/html/qemu-devel/2023-07/msg02604.html
v3:
https://lists.nongnu.org/archive/html/qemu-devel/2023-09/msg03750.html
v4:
https://lists.nongnu.org/archive/html/qemu-devel/2023-10/msg01046.html
Based-on: <20231004014532.1228637-1-stefanha@redhat.com>
([PATCH v2 0/3] vhost: clean up device reset)
Based-on: <20231016083201.23736-1-hreitz@redhat.com>
([PATCH] vhost-user: Fix protocol feature bit conflict)
Hi,
v5 is basically the same as v4, only that I’ve dropped the patch
deprecating F_STATUS (which doesn’t affect the rest of the series), that
I’ve amended the documentation in patch 1 as suggested by Stefan and
with help from Michael, and that I’ve rebased everything on top of the
F_SHARED_OBJECT changes that have been merged upstream.
git-backport-diff against v4:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/7:[0029] [FC] 'vhost-user.rst: Improve [GS]ET_VRING_BASE doc'
002/7:[----] [--] 'vhost-user.rst: Clarify enabling/disabling vrings'
003/7:[----] [--] 'vhost-user.rst: Introduce suspended state'
004/7:[0006] [FC] 'vhost-user.rst: Migrating back-end-internal state'
005/7:[0007] [FC] 'vhost-user: Interface for migration state transfer'
006/7:[----] [--] 'vhost: Add high-level state save/load functions'
007/7:[----] [--] 'vhost-user-fs: Implement internal migration'
Changes patch by patch:
- Patch 1: Amended documentation
- Patches 4 and 5: Bumped feature bit and command values as necessary so
as not to conflict with F_SHARED_OBJECT
Hanna Czenczek (7):
vhost-user.rst: Improve [GS]ET_VRING_BASE doc
vhost-user.rst: Clarify enabling/disabling vrings
vhost-user.rst: Introduce suspended state
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 | 301 ++++++++++++++++++++++++++++--
include/hw/virtio/vhost-backend.h | 24 +++
include/hw/virtio/vhost-user.h | 1 +
include/hw/virtio/vhost.h | 113 +++++++++++
hw/virtio/vhost-user-fs.c | 101 +++++++++-
hw/virtio/vhost-user.c | 146 +++++++++++++++
hw/virtio/vhost.c | 241 ++++++++++++++++++++++++
7 files changed, 906 insertions(+), 21 deletions(-)
--
2.41.0
next reply other threads:[~2023-10-16 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 13:42 Hanna Czenczek [this message]
2023-10-16 13:42 ` [Virtio-fs] [PATCH v5 1/7] vhost-user.rst: Improve [GS]ET_VRING_BASE doc Hanna Czenczek
2023-10-16 13:42 ` [Virtio-fs] [PATCH v5 2/7] vhost-user.rst: Clarify enabling/disabling vrings Hanna Czenczek
2023-10-16 13:42 ` [Virtio-fs] [PATCH v5 3/7] vhost-user.rst: Introduce suspended state Hanna Czenczek
2023-10-16 13:42 ` [Virtio-fs] [PATCH v5 4/7] vhost-user.rst: Migrating back-end-internal state Hanna Czenczek
2023-10-16 13:42 ` [Virtio-fs] [PATCH v5 5/7] vhost-user: Interface for migration state transfer Hanna Czenczek
2023-10-16 13:42 ` [Virtio-fs] [PATCH v5 6/7] vhost: Add high-level state save/load functions Hanna Czenczek
2023-10-16 13:42 ` [Virtio-fs] [PATCH v5 7/7] vhost-user-fs: Implement internal migration 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=20231016134243.68248-1-hreitz@redhat.com \
--to=hreitz@redhat.com \
--cc=antonkuchin@yandex-team.ru \
--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).