From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: owasserm@redhat.com, mtosatti@redhat.com, avi@redhat.com,
pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH 00/18] Migration thread lite (20121029)
Date: Mon, 29 Oct 2012 15:11:25 +0100 [thread overview]
Message-ID: <1351519903-26607-1-git-send-email-quintela@redhat.com> (raw)
Hi
After discussing with Anthony and Paolo, this is the minimal migration
thread support that we can do for 1.3.
- fixed all the comments (thanks eric, paolo and orit).
- buffered_file.c remains until 1.4.
- testing for vinod showed very nice results, that is why the bitmap
handling optimizations remain.
Note: Writes has become blocking, and I have to change the "remove"
the feature now in qemu-sockets.c. Checked that migration was the
only user of that feature. If new users appear, they just need to add
the socket_set_nonblock() by hand.
Please, review.
Thanks, Juan.
The following changes since commit 50cd72148211c5e5f22ea2519d19ce024226e61f:
hw/xtensa_sim: get rid of intermediate xtensa_sim_init (2012-10-27 15:04:00 +0000)
are available in the git repository at:
http://repo.or.cz/r/qemu/quintela.git migration-thread-20121029
for you to fetch changes up to 2c74654f19efc7db35117a87c0d9db4776931e1b:
ram: optimize migration bitmap walking (2012-10-29 14:14:28 +0100)
Juan Quintela (15):
buffered_file: Move from using a timer to use a thread
migration: make qemu_fopen_ops_buffered() return void
migration: stop all cpus correctly
migration: make writes blocking
migration: remove unfreeze logic
migration: take finer locking
buffered_file: Unfold the trick to restart generating migration data
buffered_file: don't flush on put buffer
buffered_file: unfold buffered_append in buffered_put_buffer
savevm: New save live migration method: pending
migration: include qemu-file.h
migration-fd: remove duplicate include
memory: introduce memory_region_test_and_clear_dirty
ram: Use memory_region_test_and_clear_dirty
ram: optimize migration bitmap walking
Paolo Bonzini (1):
split MRU ram list
Umesh Deshpande (2):
add a version number to ram_list
protect the ramlist with a separate mutex
arch_init.c | 115 ++++++++++++++++++++++++-----------------------
block-migration.c | 49 +++++---------------
buffered_file.c | 130 +++++++++++++++++++++++++-----------------------------
buffered_file.h | 2 +-
cpu-all.h | 15 ++++++-
exec.c | 44 +++++++++++++++---
memory.c | 16 +++++++
memory.h | 18 ++++++++
migration-exec.c | 3 +-
migration-fd.c | 4 +-
migration-tcp.c | 2 +-
migration-unix.c | 2 +-
migration.c | 100 ++++++++++++++++-------------------------
migration.h | 4 +-
qemu-file.h | 5 ---
qemu-sockets.c | 4 --
savevm.c | 24 +++++++---
sysemu.h | 1 +
vmstate.h | 1 +
19 files changed, 280 insertions(+), 259 deletions(-)
--
1.7.11.7
next reply other threads:[~2012-10-29 14:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 14:11 Juan Quintela [this message]
2012-10-29 14:11 ` [Qemu-devel] [PATCH 01/18] split MRU ram list Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 02/18] add a version number to ram_list Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 03/18] protect the ramlist with a separate mutex Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 04/18] buffered_file: Move from using a timer to use a thread Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 05/18] migration: make qemu_fopen_ops_buffered() return void Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 06/18] migration: stop all cpus correctly Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 07/18] migration: make writes blocking Juan Quintela
2012-10-29 15:51 ` Markus Armbruster
2012-10-29 17:32 ` Juan Quintela
2012-10-29 22:13 ` Paolo Bonzini
2012-10-30 7:36 ` Markus Armbruster
2012-10-30 8:23 ` Juan Quintela
2012-10-30 10:50 ` Markus Armbruster
2012-10-30 11:08 ` Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 08/18] migration: remove unfreeze logic Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 09/18] migration: take finer locking Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 10/18] buffered_file: Unfold the trick to restart generating migration data Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 11/18] buffered_file: don't flush on put buffer Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 12/18] buffered_file: unfold buffered_append in buffered_put_buffer Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 13/18] savevm: New save live migration method: pending Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 14/18] migration: include qemu-file.h Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 15/18] migration-fd: remove duplicate include Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 16/18] memory: introduce memory_region_test_and_clear_dirty Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 17/18] ram: Use memory_region_test_and_clear_dirty Juan Quintela
2012-10-29 14:11 ` [Qemu-devel] [PATCH 18/18] ram: optimize migration bitmap walking Juan Quintela
[not found] <4168C988EBDF2141B4E0B6475B6A73D101905D46@G6W2493.americas.hpqcorp.net>
2012-10-29 16:33 ` [Qemu-devel] [PATCH 00/18] Migration thread lite (20121029) Chegu Vinod
2012-10-29 17:33 ` 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=1351519903-26607-1-git-send-email-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=avi@redhat.com \
--cc=mtosatti@redhat.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@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 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).