Hi
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? Later, Juan. *** BLURB HERE *** Juan Quintela (1): ram: Split dirty bitmap by RAMBlock include/exec/ram_addr.h | 13 ++- include/migration/postcopy-ram.h | 3 - migration/postcopy-ram.c | 5 +- migration/ram.c | 215 +++++++++++++++------------------------ 4 files changed, 91 insertions(+), 145 deletions(-) -- 2.9.3
