qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Het Gala <het.gala@nutanix.com>
Cc: quintela@redhat.com, qemu-devel@nongnu.org,
	prerna.saxena@nutanix.com,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	pbonzini@redhat.com, Markus Armbruster <armbru@redhat.com>,
	eblake@redhat.com,
	Aravind Retnakaran <aravind.retnakaram@nutanix.com>,
	Manish Mishra <manish.mishra@nutanix.com>
Subject: Re: [PATCH] multifd: Updated QAPI format for 'migrate' qemu monitor command
Date: Wed, 23 Nov 2022 08:07:36 +0000	[thread overview]
Message-ID: <Y33UrqcTrXFMqEGl@redhat.com> (raw)
In-Reply-To: <1192c455-3a06-d4c3-0f35-0ef217fda9ec@nutanix.com>

On Wed, Nov 23, 2022 at 01:35:22AM +0530, Het Gala wrote:
> 
> On 21/11/22 6:10 pm, Juan Quintela wrote:
> > Het Gala<het.gala@nutanix.com>  wrote:
> > > To prevent double data encoding of uris, instead of passing transport
> > > mechanisms, host address and port all together in form of a single string
> > > and writing different parsing functions, we intend the user to explicitly
> > > mention most of the parameters through the medium of qmp command itself.
> > Hi
> > 
> > 1st of all, I can't see how this is 7.1 material, I guess we need to
> > move it to 8.0.
> > 
> > Thankyou for informing. I will change it to 8.0
> > > +##
> > > +# @MigrateTransport:
> > > +#
> > > +# The supported communication transport mechanisms for migration
> > > +#
> > > +# @socket: Supported communication type between two devices for migration.
> > > +#          Socket is able to cover all of 'tcp', 'unix', 'vsock' and
> > > +#          'fd' already
> > > +#
> > > +# @exec: Supported communication type to redirect migration stream into file.
> > > +#
> > > +# Since 7.1
> > > +##
> > > +{ 'enum': 'MigrateTransport',
> > > +  'data': ['socket', 'exec'] }
> > I haven't looked too much into this, but as Danield told in the past, I
> > can see where the rdma falls into this scheme.  I guess it is going to
> > be its own, but who knows.
> So do you mean, 'data' : ['socket', 'exec', 'rdma'] ? or it will be
> separately represented

Yes, you'll need an rdma entry there.  If you follow the patch split
I suggested in the other mail, you'll naturally have to represent
'rdma' in the very first patch, as you introduce the new syntax
for addresses and parse the existing URIs to map onto the new
address struct.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      reply	other threads:[~2022-11-23  8:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 11:04 [PATCH] multifd: Updated QAPI format for 'migrate' qemu monitor command Het Gala
2022-11-21 12:40 ` Juan Quintela
2022-11-22  9:23   ` Daniel P. Berrangé
2022-11-22 15:57     ` manish.mishra
2022-11-22 17:03       ` Daniel P. Berrangé
2022-11-22 20:44     ` Het Gala
2022-11-22 20:05   ` Het Gala
2022-11-23  8:07     ` Daniel P. Berrangé [this message]

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=Y33UrqcTrXFMqEGl@redhat.com \
    --to=berrange@redhat.com \
    --cc=aravind.retnakaram@nutanix.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=het.gala@nutanix.com \
    --cc=manish.mishra@nutanix.com \
    --cc=pbonzini@redhat.com \
    --cc=prerna.saxena@nutanix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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).