From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: dgilbert@redhat.com, lvivier@redhat.com, peterx@redhat.com
Subject: [Qemu-devel] [PATCH v5] Split migration bitmaps by ramblock
Date: Wed, 26 Apr 2017 09:32:46 +0200 [thread overview]
Message-ID: <20170426073247.7441-1-quintela@redhat.com> (raw)
Hi
I make it compile with DEBUG_POSTCOPY enabled.
Please review.
Later, Juan.
[v4]
Make postcopy_chunk_hostpages work at ramblock level, so we don't do
the double look over ramblocks. Tested that postcopy still works as
expected.
Later, Juan.
[v3]
I messed up previous submission and sent the wrong patch.
- This verios is a rebase on top of the ramstate series
- Fixed the problem with postcopy
Important bit is this one:
- pds->start_list[pds->cur_entry] = (start - pds->offset) * tp_size;
+ pds->start_list[pds->cur_entry] = start * tp_size;
This chunk is only used in postcopy, that is why it didn't failed
precopy tests. Once ther, just remove the start parameter and offset
member because it is not used anywhere else.
Please comment.
Later, Juan.
[v2]
For v2 this is a rebase on top of all the changes that happened in the
prvious two series.
Please, review.
[RFC]
This series split the migration and unsent bitmaps by ramblock. This
makes it easier to synchronize in small bits. This is on top of the
RAMState and not-hotplug series.
Why?
reason 1:
People have complained that by the time that we detect that a page is
sent, it has already been marked dirty "again" inside kvm, so we are
going to send it again. On top of this patch, my idea is, for words
of the bitmap that have any bit set, just synchonize the bitmap before
sending the pages. I have not looking into performance numbers yet,
jsut asking for comments about how it is done.
reason 2:
In case where the host page is a multiple of the the TARGET_PAGE_SIZE,
we do a lot of work when we are synchronizing the bitmaps to pass it
to target page size. The idea is to change the bitmaps on that
RAMBlocks to mean host page size and not TARGET_PAGE_SIZE.
Note that there are two reason for this, ARM and PPC do things like
guests with 4kb pages on hosts with 16/64kb hosts, and then we have
HugePages. Note all the workarounds that postcopy has to do because
to work in HugePages size.
Please, comment?
Juan Quintela (1):
ram: Split dirty bitmap by RAMBlock
include/exec/ram_addr.h | 13 +-
include/migration/migration.h | 3 +-
include/migration/postcopy-ram.h | 3 -
migration/postcopy-ram.c | 5 +-
migration/ram.c | 273 +++++++++++++++------------------------
5 files changed, 119 insertions(+), 178 deletions(-)
--
2.9.3
next reply other threads:[~2017-04-26 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 7:32 Juan Quintela [this message]
2017-04-26 7:32 ` [Qemu-devel] [PATCH] ram: Split dirty bitmap by RAMBlock Juan Quintela
2017-04-26 8:54 ` Hailiang Zhang
2017-04-26 10:53 ` Juan Quintela
2017-04-26 9:16 ` Peter Xu
2017-04-26 10:57 ` no-reply
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=20170426073247.7441-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 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).