Re: [Qemu-devel] [PATCH v7 17/42] Add migration-capability boolean for postcopy-ram.

[Amit Shah]

On (Tue) 16 Jun 2015 [16:58:17], Dr. David Alan Gilbert wrote:
> * Eric Blake (address@hidden) wrote:
> > On 06/16/2015 04:26 AM, Dr. David Alan Gilbert (git) wrote:
> > > From: "Dr. David Alan Gilbert" <address@hidden>
> > > 
> > > The 'postcopy ram' capability allows postcopy migration of RAM;
> > > note that the migration starts off in precopy mode until
> > > postcopy mode is triggered (see the migrate_start_postcopy
> > > patch later in the series).
> > > 
> > > Signed-off-by: Dr. David Alan Gilbert <address@hidden>
> > > ---
> > >  include/migration/migration.h |  1 +
> > >  migration/migration.c         | 23 +++++++++++++++++++++++
> > >  qapi-schema.json              |  6 +++++-
> > >  3 files changed, 29 insertions(+), 1 deletion(-)
> > > 
> > 
> > > +++ b/qapi-schema.json
> > > @@ -526,11 +526,15 @@
> > >  # @auto-converge: If enabled, QEMU will automatically throttle down the 
> > > guest
> > >  #          to speed up convergence of RAM migration. (since 1.6)
> > >  #
> > > +# @x-postcopy-ram: Start executing on the migration target before all of 
> > > RAM has
> > > +#          been migrated, pulling the remaining pages along as needed. 
> > > NOTE: If
> > > +#          the migration fails during postcopy the VM will fail.  (since 
> > > 2.4)
> > 
> > Marking it experimental because it might change?  Or is the interface
> > pretty stable, but you want more testing time to minimize bugs?
> 
> It's easy enough to remove the x-  once we're all happy;  it seems pretty
> stable at the moment but when we're done I'll just submit a one liner to take 
> the x-
> off.

We shouldn't mark it stable till we have a released kernel (which
freezes the kernel API for us).

We could pick this patchset without a released kernel, but this will
have to remain x- if that happens.

                Amit