On 08/21/2011 03:41 AM, Umesh Deshpande wrote:
This should be run under the iothread lock. Pay attention to avoiding
lock inversion: the I/O thread always takes the iothread lock outside
and the ramlist lock within, so the migration thread must do the same.
BTW, I think this code in the migrat
On 08/19/2011 08:51 AM, Paolo Bonzini wrote:
On 08/16/2011 08:56 PM, Umesh Deshpande wrote:
@@ -2128,8 +2132,61 @@ void
cpu_physical_memory_reset_dirty(ram_addr_t start, ram_addr_t end,
start1, length);
}
}
+
}
+void migration_bitmap_reset_
On 08/16/2011 08:56 PM, Umesh Deshpande wrote:
@@ -2128,8 +2132,61 @@ void cpu_physical_memory_reset_dirty(ram_addr_t start,
ram_addr_t end,
start1, length);
}
}
+
}
+void migration_bitmap_reset_dirty(ram_addr_t start, ram_addr_t end,
+
This patch creates a migration bitmap, which is periodically kept in sync with
the qemu bitmap. A separate copy of the dirty bitmap for the migration avoids
concurrent access to the qemu bitmap from iothread and migration thread.
Signed-off-by: Umesh Deshpande
---
arch_init.c | 26
