qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 00/14] migration queue
Date: Tue, 15 Jan 2013 12:50:53 -0700	[thread overview]
Message-ID: <50F5B31D.7080200@redhat.com> (raw)
In-Reply-To: <1358248702-14278-1-git-send-email-quintela@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

On 01/15/2013 04:18 AM, Juan Quintela wrote:
> Hi
> 
> This is the intersect of the paolo & me patches for migration thread,
> please consided for inclusion.
> 

> 
>  arch_init.c                   |   6 +-
>  include/migration/migration.h |   3 -
>  include/sysemu/sysemu.h       |   2 +-
>  migration.c                   | 183 ++++++++++++++++++++----------------------
>  savevm.c                      |  12 +--
>  5 files changed, 98 insertions(+), 108 deletions(-)

I found some commit message improvements in 3 and 8, but as that does
not affect the code...

Series: Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  parent reply	other threads:[~2013-01-15 19:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 11:18 [Qemu-devel] [PATCH 00/14] migration queue Juan Quintela
2013-01-15 11:18 ` [Qemu-devel] [PATCH 01/14] Unlock ramlist lock also in error case Juan Quintela
2013-01-15 11:18 ` [Qemu-devel] [PATCH 02/14] Protect migration_bitmap_sync() with the ramlist lock Juan Quintela
2013-01-15 11:18 ` [Qemu-devel] [PATCH 03/14] use XFER_LIMIT_RATIO consistently Juan Quintela
2013-01-15 19:45   ` Eric Blake
2013-01-15 11:18 ` [Qemu-devel] [PATCH 04/14] migration: make function static Juan Quintela
2013-01-15 11:18 ` [Qemu-devel] [PATCH 05/14] migration: remove double call to migrate_fd_close Juan Quintela
2013-01-15 11:18 ` [Qemu-devel] [PATCH 06/14] migration: fix off-by-one in buffered_rate_limit Juan Quintela
2013-01-15 11:18 ` [Qemu-devel] [PATCH 07/14] qemu-file: Only set last_error if it is not already set Juan Quintela
2013-01-15 11:18 ` [Qemu-devel] [PATCH 08/14] migration: move begining stage to the migration thread Juan Quintela
2013-01-15 19:47   ` Eric Blake
2013-01-15 11:18 ` [Qemu-devel] [PATCH 09/14] migration: Add buffered_flush error handling Juan Quintela
2013-01-15 11:18 ` [Qemu-devel] [PATCH 10/14] migration: move exit condition to migration thread Juan Quintela
2013-01-15 11:18 ` [Qemu-devel] [PATCH 11/14] migration: unfold rest of migrate_fd_put_ready() into thread Juan Quintela
2013-01-15 11:18 ` [Qemu-devel] [PATCH 12/14] migration: Only go to the iterate stage if there is anything to send Juan Quintela
2013-01-15 11:18 ` [Qemu-devel] [PATCH 13/14] migration: remove argument to qemu_savevm_state_cancel Juan Quintela
2013-01-15 11:18 ` [Qemu-devel] [PATCH 14/14] Rename buffered_ to migration_ Juan Quintela
2013-01-15 15:12   ` Paolo Bonzini
2013-01-15 19:50 ` Eric Blake [this message]
2013-01-16 18:14 ` [Qemu-devel] [PATCH 00/14] migration queue Anthony Liguori
2013-01-17 10:50   ` Paolo Bonzini
2013-01-17 12:46     ` Juan Quintela
2013-01-17 13:00       ` 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=50F5B31D.7080200@redhat.com \
    --to=eblake@redhat.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).