All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: chegu_vinod@hp.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC v2] Migration thread
Date: Fri, 07 Sep 2012 21:52:57 +0200	[thread overview]
Message-ID: <87627pliee.fsf@elfo.mitica> (raw)
In-Reply-To: <504A2A1F.8090703@redhat.com> (Paolo Bonzini's message of "Fri, 07 Sep 2012 19:08:47 +0200")

Paolo Bonzini <pbonzini@redhat.com> wrote:
> Il 07/09/2012 18:23, Juan Quintela ha scritto:
>> 
>> Hi
>> 
>> here is v2 of the migration thread series.  There is still some "issues"
>> with locking in the error paths (they are at 54 patches now).
>> 
>> Changes from v1:
>> - migration stats series are included
>> - migration bitmap sync trace-events to know how long it takes
>> - file->last_error use almost removed
>>   reworked functions to return real error codes and work with that.
>>   Some more work needed here.
>> - new savevm for live migration pending method.  see last commit for
>> details.
>
> Can you start factoring out any cleanup that can be applied independently?

This is the breakpoint.

  buffered_file: Move from using a timer to use a thread

Everything before this could be integrated Today, from there, it needs
still more 'thought".

As said, buffered_file.c is almost gone, and file->last_error is almost
gone.  That were the things that I wanted to clean to be able to split
the generation of migration data and its writting.

Later, Juan.

  reply	other threads:[~2012-09-07 19:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 16:23 [Qemu-devel] [RFC v2] Migration thread Juan Quintela
2012-09-07 17:08 ` Paolo Bonzini
2012-09-07 19:52   ` Juan Quintela [this message]
2012-09-07 20:29     ` Paolo Bonzini

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=87627pliee.fsf@elfo.mitica \
    --to=quintela@redhat.com \
    --cc=chegu_vinod@hp.com \
    --cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.