From: Peter Xu <peterx@redhat.com>
To: Het Gala <het.gala@nutanix.com>
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH] qapi: Misc cleanups to migrate QAPIs
Date: Wed, 21 Feb 2024 16:26:01 +0800 [thread overview]
Message-ID: <ZdWzmbOuCVk8GZMn@x1n> (raw)
In-Reply-To: <b1ce8254-24e8-487e-8da0-d8916f53fcb4@nutanix.com>
Thanks, Markus.
On Wed, Feb 21, 2024 at 12:36:57PM +0530, Het Gala wrote:
> > > diff --git a/qapi/migration.json b/qapi/migration.json
> > > index 5a565d9b8d..5756e650b0 100644
> > > --- a/qapi/migration.json
> > > +++ b/qapi/migration.json
> > > @@ -1728,6 +1728,7 @@
> > > #
> > > # -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
> > > # <- { "return": {} }
> > > +#
> > > # -> { "execute": "migrate",
> > > # "arguments": {
> > > # "channels": [ { "channel-type": "main",
> > > @@ -1796,19 +1797,19 @@
> > > #
> > > # 3. The uri format is the same as for -incoming
> > > #
> > > -# 5. For now, number of migration streams is restricted to one,
> > > +# 4. For now, number of migration streams is restricted to one,
> > > # i.e number of items in 'channels' list is just 1.
> > > #
> > > -# 4. The 'uri' and 'channels' arguments are mutually exclusive;
> > > +# 5. The 'uri' and 'channels' arguments are mutually exclusive;
> > > # exactly one of the two should be present.
> > > #
> > > # Example:
> > > #
> > > # -> { "execute": "migrate-incoming",
> > > -# "arguments": { "uri": "tcp::4446" } }
> > > +# "arguments": { "uri": "tcp:0:4446" } }
> > > # <- { "return": {} }
> > > #
> > > -# -> { "execute": "migrate",
> > > +# -> { "execute": "migrate-incoming",
> > > # "arguments": {
> > > # "channels": [ { "channel-type": "main",
> > > # "addr": { "transport": "socket",
> > > @@ -1817,7 +1818,7 @@
> > > # "port": "1050" } } ] } }
> > > # <- { "return": {} }
> > > #
> > > -# -> { "execute": "migrate",
> > > +# -> { "execute": "migrate-incoming",
> > > # "arguments": {
> > > # "channels": [ { "channel-type": "main",
> > > # "addr": { "transport": "exec",
> > > @@ -1825,7 +1826,7 @@
> > > # "/some/sock" ] } } ] } }
> > > # <- { "return": {} }
> > > #
> > > -# -> { "execute": "migrate",
> > > +# -> { "execute": "migrate-incoming",
> > > # "arguments": {
> > > # "channels": [ { "channel-type": "main",
> > > # "addr": { "transport": "rdma",
Reviewed-by: Peter Xu <peterx@redhat.com>
Markus, do you want us to pick it up, or let it go via qapi?
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2024-02-21 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 19:56 [PATCH] qapi: Misc cleanups to migrate QAPIs Het Gala
2024-02-21 6:57 ` Markus Armbruster
2024-02-21 7:06 ` Het Gala
2024-02-21 8:23 ` Markus Armbruster
2024-02-21 8:26 ` Peter Xu [this message]
2024-02-21 8:30 ` Markus Armbruster
2024-02-21 9:58 ` Peter Xu
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=ZdWzmbOuCVk8GZMn@x1n \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=farosas@suse.de \
--cc=het.gala@nutanix.com \
--cc=qemu-devel@nongnu.org \
/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).