From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: dgilbert@redhat.com, lvivier@redhat.com, peterx@redhat.com
Subject: [Qemu-devel] [PULL 0/5] Migration pull request
Date: Mon, 4 Jun 2018 06:21:51 +0200 [thread overview]
Message-ID: <20180604042156.13812-1-quintela@redhat.com> (raw)
The following changes since commit 392fba9f583223786f844dce9b2e7f9a0ce0147a:
Merge remote-tracking branch 'remotes/stsquad/tags/pull-travis-updates-010618-1' into staging (2018-06-01 17:32:30 +0100)
are available in the Git repository at:
git://github.com/juanquintela/qemu.git tags/migration/20180604
for you to fetch changes up to c5e76115ccb4979cec795a8ae38becd07c2fde9f:
migration: not wait RDMA_CM_EVENT_DISCONNECTED event after rdma_disconnect (2018-06-04 05:46:15 +0200)
----------------------------------------------------------------
migration/next for 20180604
- RDMA fixes from (lidong)
- Fix docempress-error-check (Xiao)
- make -S and block work better (dave)
- don't migrate "bad" ramblocks (Cédric)
Please apply, Juan.
----------------------------------------------------------------
Cédric Le Goater (1):
migration: discard non-migratable RAMBlocks
Dr. David Alan Gilbert (1):
migration: Don't activate block devices if using -S
Lidong Chen (2):
migration: remove unnecessary variables len in QIOChannelRDMA
migration: not wait RDMA_CM_EVENT_DISCONNECTED event after rdma_disconnect
Xiao Guangrong (1):
migration: introduce decompress-error-check
exec.c | 38 +++++++++++++++++++++++++++++++++++++
hw/arm/virt.c | 4 ++++
hw/i386/pc_piix.c | 1 +
hw/i386/pc_q35.c | 1 +
include/exec/cpu-common.h | 4 ++++
include/hw/compat.h | 7 ++++++-
migration/migration.c | 38 ++++++++++++++++++++++++++++++-------
migration/migration.h | 7 +++++++
migration/postcopy-ram.c | 12 ++++++------
migration/ram.c | 48 ++++++++++++++++++++++++++++++++++-------------
migration/rdma.c | 27 +++++++++-----------------
migration/savevm.c | 2 ++
migration/trace-events | 1 -
qapi/migration.json | 6 +++++-
14 files changed, 149 insertions(+), 47 deletions(-)
next reply other threads:[~2018-06-04 4:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 4:21 Juan Quintela [this message]
2018-06-04 4:21 ` [Qemu-devel] [PULL 1/5] migration: introduce decompress-error-check Juan Quintela
2018-06-04 4:21 ` [Qemu-devel] [PULL 2/5] migration: discard non-migratable RAMBlocks Juan Quintela
2018-06-04 4:21 ` [Qemu-devel] [PULL 3/5] migration: Don't activate block devices if using -S Juan Quintela
2018-06-04 4:21 ` [Qemu-devel] [PULL 4/5] migration: remove unnecessary variables len in QIOChannelRDMA Juan Quintela
2018-06-04 4:21 ` [Qemu-devel] [PULL 5/5] migration: not wait RDMA_CM_EVENT_DISCONNECTED event after rdma_disconnect Juan Quintela
2018-06-04 4:29 ` [Qemu-devel] [PULL 0/5] Migration pull request no-reply
2018-06-04 7:30 ` Juan Quintela
2018-06-04 13:24 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2017-06-14 11:51 [Qemu-devel] [PULL 0/5] Migration PULL request Juan Quintela
2017-06-15 11:56 ` Peter Maydell
2017-05-31 9:15 [Qemu-devel] [PULL 0/5] Migration pull request Juan Quintela
2017-06-01 14:50 ` Peter Maydell
2017-05-12 15:52 Juan Quintela
2017-05-15 13:58 ` Stefan Hajnoczi
2017-05-15 14:52 ` Eric Blake
2017-05-15 17:17 ` Juan Quintela
2017-05-16 14:35 ` Stefan Hajnoczi
2015-11-04 12:48 Juan Quintela
2015-11-05 10:48 ` 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=20180604042156.13812-1-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=peterx@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.