On 08/23/2011 10:12 PM, Umesh Deshpande wrote:
Following patch series deals with VCPU and iothread starvation during the migration of a guest. Currently the iothread is responsible for performing the guest migration. It holds qemu_mutex during the migration and doesn't allow VCPU to enter the qemu mode and delays its return to the guest. The guest migration, executed as an iohandler also delays the execution of other iohandlers. In the following patch series,
Can you please include detailed performance data with and without this series?
Perhaps runs of migration with jitterd running in the guest. Regards, Anthony Liguori
The migration has been moved to a separate thread to reduce the qemu_mutex contention and iohandler starvation. Umesh Deshpande (4): MRU ram block list migration thread mutex separate migration bitmap separate migration thread arch_init.c | 38 ++++++++++++---- buffered_file.c | 75 +++++++++++++++++-------------- cpu-all.h | 42 +++++++++++++++++ exec.c | 97 ++++++++++++++++++++++++++++++++++++++-- migration.c | 122 +++++++++++++++++++++++++++++--------------------- migration.h | 9 ++++ qemu-common.h | 2 + qemu-thread-posix.c | 10 ++++ qemu-thread.h | 1 + savevm.c | 5 -- 10 files changed, 297 insertions(+), 104 deletions(-)
-- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
