From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
Thomas Huth <thuth@redhat.com>,
zhanghailiang <zhang.zhanghailiang@huawei.com>,
Juan Quintela <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PULL 0/5] Migration patches
Date: Wed, 5 Jun 2019 13:53:13 +0200 [thread overview]
Message-ID: <20190605115318.9972-1-quintela@redhat.com> (raw)
The following changes since commit 47fbad45d47af8af784bb12a5719489edcd89b4c:
Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging (2019-06-04 17:22:42 +0100)
are available in the Git repository at:
https://github.com/juanquintela/qemu.git tags/migration-pull-request
for you to fetch changes up to 03158519384f15890d587937bd1b3ea699898e55:
migratioin/ram: leave RAMBlock->bmap blank on allocating (2019-06-05 12:44:03 +0200)
----------------------------------------------------------------
Migration Pull request
- Fd fixes and test (yuri)
- several fixes (wei)
----------------------------------------------------------------
Wei Yang (3):
migration/ram.c: MultiFDSendParams.sem_sync is not really used
migration/ram.c: multifd_send_state->count is not really used
migratioin/ram: leave RAMBlock->bmap blank on allocating
Yury Kotov (2):
migration: Fix fd protocol for incoming defer
migration-test: Add a test for fd protocol
migration/fd.c | 8 ++--
migration/fd.h | 2 +-
migration/ram.c | 27 ++++++-----
tests/libqtest.c | 80 ++++++++++++++++++++++++++++++--
tests/libqtest.h | 51 ++++++++++++++++++++-
tests/migration-test.c | 101 +++++++++++++++++++++++++++++++++++++++++
6 files changed, 246 insertions(+), 23 deletions(-)
--
2.21.0
next reply other threads:[~2019-06-05 11:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 11:53 Juan Quintela [this message]
2019-06-05 11:53 ` [Qemu-devel] [PULL 1/5] migration/ram.c: MultiFDSendParams.sem_sync is not really used Juan Quintela
2019-06-05 11:53 ` [Qemu-devel] [PULL 2/5] migration/ram.c: multifd_send_state->count " Juan Quintela
2019-06-05 11:53 ` [Qemu-devel] [PULL 3/5] migration: Fix fd protocol for incoming defer Juan Quintela
2019-06-05 11:53 ` [Qemu-devel] [PULL 4/5] migration-test: Add a test for fd protocol Juan Quintela
2019-06-05 11:53 ` [Qemu-devel] [PULL 5/5] migratioin/ram: leave RAMBlock->bmap blank on allocating Juan Quintela
2019-06-05 12:26 ` Philippe Mathieu-Daudé
2019-06-05 13:36 ` Wei Yang
2019-06-05 13:37 ` Wei Yang
2019-06-06 10:32 ` [Qemu-devel] [PULL 0/5] Migration patches 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=20190605115318.9972-1-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=zhang.zhanghailiang@huawei.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).