From: Amit Shah <amit.shah@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Juan Quintela <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
qemu list <qemu-devel@nongnu.org>,
Amit Shah <amit.shah@redhat.com>
Subject: [Qemu-devel] [PULL 0/8] migration: fixes
Date: Fri, 10 Jun 2016 12:30:44 +0530 [thread overview]
Message-ID: <cover.1465541858.git.amit.shah@redhat.com> (raw)
The following changes since commit 0c33682d5f29b0a4ae53bdec4c8e52e4fae37b34:
target-i386: Move user-mode exception actions out of user-exec.c (2016-06-09 15:55:02 +0100)
are available in the git repository at:
https://git.kernel.org/pub/scm/virt/qemu/amit/migration.git tags/migration-for-2.7-2
for you to fetch changes up to 05db906b8a77df70922e836d629c7f545b97dad7:
migration: rename functions to starting migrations (2016-06-10 12:12:32 +0530)
----------------------------------------------------------------
Migration:
- Fixes for TLS series
- Postcopy: Add stats, fix, test case
----------------------------------------------------------------
Andrea Arcangeli (1):
tests: fix libqtest socket timeouts
Daniel P. Berrange (2):
migration: fix typos in qapi-schema from latest migration additions
migration: rename functions to starting migrations
Dr. David Alan Gilbert (5):
Postcopy: Avoid 0 length discards
Migration: Split out ram part of qmp_query_migrate
Postcopy: Add stats on page requests
test: Postcopy
Postcopy: Check for support when setting the capability
hmp.c | 4 +
include/migration/migration.h | 28 +--
migration/exec.c | 4 +-
migration/fd.c | 4 +-
migration/migration.c | 91 +++++----
migration/ram.c | 5 +-
migration/rdma.c | 4 +-
migration/socket.c | 6 +-
migration/tls.c | 18 +-
qapi-schema.json | 16 +-
tests/Makefile.include | 2 +
tests/libqtest.c | 2 +-
tests/postcopy-test.c | 455 ++++++++++++++++++++++++++++++++++++++++++
13 files changed, 556 insertions(+), 83 deletions(-)
create mode 100644 tests/postcopy-test.c
--
2.7.4
next reply other threads:[~2016-06-10 7:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 7:00 Amit Shah [this message]
2016-06-10 7:00 ` [Qemu-devel] [PULL 1/8] Postcopy: Avoid 0 length discards Amit Shah
2016-06-10 7:00 ` [Qemu-devel] [PULL 2/8] Migration: Split out ram part of qmp_query_migrate Amit Shah
2016-06-10 7:00 ` [Qemu-devel] [PULL 3/8] Postcopy: Add stats on page requests Amit Shah
2016-06-10 7:00 ` [Qemu-devel] [PULL 4/8] test: Postcopy Amit Shah
2016-06-10 7:00 ` [Qemu-devel] [PULL 5/8] tests: fix libqtest socket timeouts Amit Shah
2016-06-10 7:00 ` [Qemu-devel] [PULL 6/8] Postcopy: Check for support when setting the capability Amit Shah
2016-06-10 7:00 ` [Qemu-devel] [PULL 7/8] migration: fix typos in qapi-schema from latest migration additions Amit Shah
2016-06-10 7:00 ` [Qemu-devel] [PULL 8/8] migration: rename functions to starting migrations Amit Shah
2016-06-10 9:55 ` [Qemu-devel] [PULL 0/8] migration: fixes Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2016-06-10 11:48 Amit Shah
2016-06-10 13:25 ` Peter Maydell
2016-06-10 13:51 ` Peter Maydell
2016-06-10 19:09 ` Dr. David Alan Gilbert
2016-06-10 13:57 ` Dr. David Alan Gilbert
2016-06-16 4:43 Amit Shah
2016-06-16 11:39 ` 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=cover.1465541858.git.amit.shah@redhat.com \
--to=amit.shah@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=peter.maydell@linaro.org \
--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).