From: Amit Shah <amit.shah@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>, qemu list <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [migration PULL 0/9] Migration queue - for Juan
Date: Tue, 29 Sep 2015 12:02:15 +0530 [thread overview]
Message-ID: <cover.1443508205.git.amit.shah@redhat.com> (raw)
Hi Juan,
Here are a few patches from the list that have been reviewed by at
least one person.
Would be great to have your review and then a pull.
Thanks,
The following changes since commit 9e071429e649346c14b2dc76902f84f8352d2333:
Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2015-09-25 21:52:30 +0100)
are available in the git repository at:
https://git.kernel.org/pub/scm/virt/qemu/amit/migration.git tags/for-juan-201509
for you to fetch changes up to b9e6092814735853cc1149e2e68245b09f621306:
ram_find_and_save_block: Split out the finding (2015-09-29 11:38:29 +0530)
----------------------------------------------------------------
Migration queue
----------------------------------------------------------------
Dr. David Alan Gilbert (7):
migration/ram.c: Use RAMBlock rather than MemoryRegion
Split out end of migration code from migration_thread
Init page sizes in qtest
migration: size_t'ify some of qemu-file
migration: qemu-file more size_t'ifying
Move dirty page search state into separate structure
ram_find_and_save_block: Split out the finding
Markus Armbruster (1):
migration: Use g_new() & friends where that makes obvious sense
Soren Brinkmann (1):
vmstate: Remove redefinition of VMSTATE_UINT32_ARRAY
include/migration/qemu-file.h | 18 +++---
include/migration/vmstate.h | 3 -
migration/migration.c | 77 ++++++++++++++---------
migration/qemu-file-buf.c | 9 +--
migration/qemu-file-stdio.c | 15 ++---
migration/qemu-file-unix.c | 10 +--
migration/qemu-file.c | 24 +++----
migration/ram.c | 143 +++++++++++++++++++++++++++---------------
migration/rdma.c | 30 ++++-----
migration/savevm.c | 19 +++---
qtest.c | 1 +
trace-events | 4 +-
12 files changed, 211 insertions(+), 142 deletions(-)
--
2.4.3
next reply other threads:[~2015-09-29 6:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 6:32 Amit Shah [this message]
2015-09-29 6:32 ` [Qemu-devel] [migration PULL 1/9] vmstate: Remove redefinition of VMSTATE_UINT32_ARRAY Amit Shah
2015-09-29 6:32 ` [Qemu-devel] [migration PULL 2/9] migration/ram.c: Use RAMBlock rather than MemoryRegion Amit Shah
2015-09-29 6:32 ` [Qemu-devel] [migration PULL 3/9] Split out end of migration code from migration_thread Amit Shah
2015-09-29 6:32 ` [Qemu-devel] [migration PULL 4/9] Init page sizes in qtest Amit Shah
2015-09-29 6:32 ` [Qemu-devel] [migration PULL 5/9] migration: size_t'ify some of qemu-file Amit Shah
2015-09-29 6:32 ` [Qemu-devel] [migration PULL 6/9] migration: qemu-file more size_t'ifying Amit Shah
2015-09-29 6:32 ` [Qemu-devel] [migration PULL 7/9] migration: Use g_new() & friends where that makes obvious sense Amit Shah
2015-09-29 6:32 ` [Qemu-devel] [migration PULL 8/9] Move dirty page search state into separate structure Amit Shah
2015-09-29 6:32 ` [Qemu-devel] [migration PULL 9/9] ram_find_and_save_block: Split out the finding Amit Shah
2015-09-29 12:50 ` [Qemu-devel] [migration PULL 0/9] Migration queue - for Juan Peter Maydell
2015-09-29 13:05 ` Amit Shah
2015-09-29 13:23 ` Peter Maydell
2015-09-30 16:23 ` 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=cover.1443508205.git.amit.shah@redhat.com \
--to=amit.shah@redhat.com \
--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 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.