From: Stefan Hajnoczi <stefanha@redhat.com>
To: Anton Kuchin <antonkuchin@yandex-team.ru>
Cc: qemu-devel@nongnu.org, yc-core@yandex-team.ru,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Juan Quintela" <quintela@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
virtio-fs@redhat.com, "Eric Blake" <eblake@redhat.com>
Subject: Re: [PATCH v3 1/1] vhost-user-fs: add migration type property
Date: Tue, 21 Feb 2023 15:45:38 -0500 [thread overview]
Message-ID: <Y/UtctcE2Zz6fN/m@fedora> (raw)
In-Reply-To: <20230217170038.1273710-2-antonkuchin@yandex-team.ru>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Fri, Feb 17, 2023 at 07:00:38PM +0200, Anton Kuchin wrote:
> Migration of vhost-user-fs device requires transfer of FUSE internal state
> from backend. There is no standard way to do it now so by default migration
> must be blocked. But if this state can be externally transferred by
> orchestrator give it an option to explicitly allow migration.
>
> Signed-off-by: Anton Kuchin <antonkuchin@yandex-team.ru>
> ---
> hw/core/qdev-properties-system.c | 10 +++++++++
> hw/virtio/vhost-user-fs.c | 32 ++++++++++++++++++++++++++++-
> include/hw/qdev-properties-system.h | 1 +
> include/hw/virtio/vhost-user-fs.h | 2 ++
> qapi/migration.json | 16 +++++++++++++++
> 5 files changed, 60 insertions(+), 1 deletion(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-02-21 20:46 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 17:00 [PATCH v3 0/1] virtio-fs: implement option for stateless migration Anton Kuchin
2023-02-17 17:00 ` [PATCH v3 1/1] vhost-user-fs: add migration type property Anton Kuchin
2023-02-21 20:45 ` Stefan Hajnoczi [this message]
2023-02-22 12:20 ` Vladimir Sementsov-Ogievskiy
2023-02-22 12:43 ` Michael S. Tsirkin
2023-02-22 14:25 ` Anton Kuchin
2023-02-22 15:14 ` Vladimir Sementsov-Ogievskiy
2023-02-22 16:43 ` Michael S. Tsirkin
2023-02-22 17:15 ` Anton Kuchin
2023-02-22 17:30 ` Michael S. Tsirkin
2023-02-22 16:49 ` Anton Kuchin
2023-02-22 16:51 ` Michael S. Tsirkin
2023-02-22 17:05 ` Anton Kuchin
2023-02-22 17:12 ` Michael S. Tsirkin
2023-02-22 18:25 ` Anton Kuchin
2023-02-22 20:21 ` Michael S. Tsirkin
2023-02-22 20:50 ` Anton Kuchin
2023-03-01 15:40 ` Michael S. Tsirkin
2023-02-23 7:36 ` Michael S. Tsirkin
2023-02-23 21:24 ` Stefan Hajnoczi
2023-02-24 4:14 ` Anton Kuchin
2023-02-27 10:19 ` Anton Kuchin
2023-02-24 8:47 ` Michael S. Tsirkin
2023-02-28 14:30 ` Anton Kuchin
2023-02-28 14:57 ` Michael S. Tsirkin
2023-02-28 17:59 ` Anton Kuchin
2023-02-28 21:24 ` Michael S. Tsirkin
2023-03-01 14:03 ` Vladimir Sementsov-Ogievskiy
2023-03-01 14:46 ` Michael S. Tsirkin
2023-03-01 15:40 ` Anton Kuchin
2023-03-01 15:52 ` Michael S. Tsirkin
2023-03-01 16:29 ` Anton Kuchin
2023-03-01 17:19 ` Michael S. Tsirkin
2023-03-01 19:42 ` Anton Kuchin
2023-03-01 15:07 ` Anton Kuchin
2023-03-01 15:24 ` Michael S. Tsirkin
2023-03-01 16:04 ` Anton Kuchin
2023-03-01 17:17 ` Michael S. Tsirkin
2023-03-01 19:35 ` Anton Kuchin
2023-03-01 20:22 ` Michael S. Tsirkin
2023-03-06 20:55 ` Anton Kuchin
2023-03-06 21:53 ` Michael S. Tsirkin
2023-03-17 18:04 ` Anton Kuchin
2023-03-01 15:33 ` Michael S. Tsirkin
2023-03-17 19:02 ` Anton Kuchin
2023-02-28 19:18 ` Stefan Hajnoczi
2023-02-28 21:29 ` Michael S. Tsirkin
2023-02-28 21:54 ` Michael S. Tsirkin
2023-02-22 14:21 ` Anton Kuchin
2023-02-22 15:15 ` Vladimir Sementsov-Ogievskiy
2023-02-22 15:20 ` Vladimir Sementsov-Ogievskiy
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=Y/UtctcE2Zz6fN/m@fedora \
--to=stefanha@redhat.com \
--cc=antonkuchin@yandex-team.ru \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=virtio-fs@redhat.com \
--cc=yc-core@yandex-team.ru \
/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).