aboutsummaryrefslogtreecommitdiff
path: root/util/coroutine-win32.c
diff options
context:
space:
mode:
authorYury Kotov <yury-kotov@yandex-team.ru>2019-11-25 16:36:32 +0300
committerJuan Quintela <quintela@redhat.com>2020-01-20 09:10:22 +0100
commite65cec5e5d97927d22b39167d3e8edeffc771788 (patch)
tree65baa09279886e048f10dd353e5155108e691973 /util/coroutine-win32.c
parent174723ffe586e453f8ed4010ea07bbf79805b63f (diff)
downloadqemu-e65cec5e5d97927d22b39167d3e8edeffc771788.zip
qemu-e65cec5e5d97927d22b39167d3e8edeffc771788.tar.gz
qemu-e65cec5e5d97927d22b39167d3e8edeffc771788.tar.bz2
migration/ram: Yield periodically to the main loop
Usually, incoming migration coroutine yields to the main loop while its IO-channel is waiting for data to receive. But there is a case when RAM migration and data receive have the same speed: VM with huge zeroed RAM. In this case, IO-channel won't read and thus the main loop is stuck and for instance, it doesn't respond to QMP commands. For this case, yield periodically, but not too often, so as not to affect the speed of migration. Signed-off-by: Yury Kotov <yury-kotov@yandex-team.ru> Reviewed-by: Juan Quintela <quintela@redhat.com> Signed-off-by: Juan Quintela <quintela@redhat.com>
Diffstat (limited to 'util/coroutine-win32.c')
0 files changed, 0 insertions, 0 deletions