qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>
Subject: [Qemu-devel] [PULL 0/4] migration queue
Date: Tue,  9 Apr 2013 15:09:21 +0200	[thread overview]
Message-ID: <1365512961-15623-1-git-send-email-quintela@redhat.com> (raw)

Hi

Anthony,  this inculed the iovec patches that help savevm performance by paolo.  Please pull.

Later,  Juan.


The following changes since commit 47b5264eb3e1cd2825e48d28fd0d1b239ed53974:

  Merge remote-tracking branch 'bonzini/hw-dirs' into staging (2013-04-08 13:12:33 -0500)

are available in the git repository at:


  git://github.com/juanquintela/qemu.git migration.next

for you to fetch changes up to 4d1172472cdf28a444321ca8b165ce7326eb919e:

  migration: simplify writev vs. non-writev logic (2013-04-09 15:00:13 +0200)

----------------------------------------------------------------
Paolo Bonzini (4):
      migration: set f->is_write and flush in add_to_iovec
      migration: use a single I/O operation when writev_buffer is not defined
      migration: drop is_write complications
      migration: simplify writev vs. non-writev logic

 savevm.c | 104 ++++++++++++++++++++++++++-------------------------------------
 1 file changed, 42 insertions(+), 62 deletions(-)

             reply	other threads:[~2013-04-09 13:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 13:09 Juan Quintela [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-25 14:07 [Qemu-devel] [PULL 0/4] migration queue Juan Quintela
2014-02-26 22:55 ` Peter Maydell
2014-03-08 21:32 Juan Quintela
2014-03-10 12:36 ` Peter Maydell
2014-06-10 16:31 Juan Quintela
2014-06-10 16:41 ` Paolo Bonzini
2014-06-11 10:20   ` Juan Quintela
2014-06-11 14:35 ` Peter Maydell
2014-06-12 12:13   ` Juan Quintela

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=1365512961-15623-1-git-send-email-quintela@redhat.com \
    --to=quintela@redhat.com \
    --cc=aliguori@us.ibm.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).