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 00/22] migration queue
Date: Tue, 26 Mar 2013 15:43:23 +0100	[thread overview]
Message-ID: <1364309003-10701-1-git-send-email-quintela@redhat.com> (raw)

Hi Anthony

This pull request include:

- Peter Lieven zero page optimizations
- David Gibson new VMSTATE macros
- Orit asynchronous writes.
- migration documentation (me)

All of them have had several rounds through qemu-devel@

Please, pull.

Later, Juan.


The following changes since commit dcadaa9b40d6019ac18d6fd7763d43048ef79218:

  Merge remote-tracking branch 'stefanha/net' into staging (2013-03-25 13:14:26 -0500)

are available in the git repository at:


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

for you to fetch changes up to 500f0061d628b52220038939728f0d7aee634468:

  Use qemu_put_buffer_async for guest memory pages (2013-03-26 13:32:33 +0100)

----------------------------------------------------------------
David Gibson (5):
      savevm: Add VMSTATE_UINT64_EQUAL helpers
      savevm: Add VMSTATE_UINTTL_EQUAL helper
      savevm: Add VMSTATE_FLOAT64 helpers
      savevm: Add VMSTATE_STRUCT_VARRAY_POINTER_UINT32
      savevm: Fix bugs in the VMSTATE_VBUFFER_MULTIPLY definition

Juan Quintela (1):
      migration: Improve QMP documentation

Orit Wasserman (7):
      Add QemuFileWritevBuffer QemuFileOps
      Add socket_writev_buffer function
      Update bytes_xfer in qemu_put_byte
      Store the data to send also in iovec
      Use writev ops if available
      Add qemu_put_buffer_async
      Use qemu_put_buffer_async for guest memory pages

Peter Lieven (9):
      move vector definitions to qemu-common.h
      cutils: add a function to find non-zero content in a buffer
      buffer_is_zero: use vector optimizations if possible
      bitops: unroll while loop in find_next_bit()
      migration: search for zero instead of dup pages
      migration: add an indicator for bulk state of ram migration
      migration: do not sent zero pages in bulk stage
      migration: do not search dirty pages in bulk stage
      migration: use XBZRLE only after bulk stage

 arch_init.c                   |  76 +++++++++++-----------
 hmp.c                         |   2 +
 hw/hw.h                       |   6 ++
 include/migration/migration.h |   2 +
 include/migration/qemu-file.h |  12 ++++
 include/migration/vmstate.h   |  43 +++++++++++--
 include/qemu-common.h         |  31 +++++++++
 migration.c                   |   3 +-
 qapi-schema.json              |   8 ++-
 qmp-commands.hx               |  55 +++++++++-------
 savevm.c                      | 146 +++++++++++++++++++++++++++++++++++++-----
 util/bitops.c                 |  18 +++++-
 util/cutils.c                 |  60 +++++++++++++++++
 13 files changed, 375 insertions(+), 87 deletions(-)

             reply	other threads:[~2013-03-26 14:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 14:43 Juan Quintela [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-24 13:09 [Qemu-devel] [PULL 00/22] Migration queue Juan Quintela
2014-06-24 15:10 ` Peter Maydell
2019-03-06 11:42 [Qemu-devel] [PULL 00/22] migration queue Dr. David Alan Gilbert (git)
2019-03-06 12:06 ` no-reply
2019-03-06 16:23 ` Peter Maydell

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=1364309003-10701-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).