aboutsummaryrefslogtreecommitdiff
path: root/hw/misc/arm_l2x0.c
diff options
context:
space:
mode:
authorVladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>2020-07-27 22:42:18 +0300
committerEric Blake <eblake@redhat.com>2020-07-27 15:39:58 -0500
commit09feea6cf528b3158640d6530174cf21cb579bc0 (patch)
tree3e360c680b17fb22e75e7e1380f62783cd5a0f5d /hw/misc/arm_l2x0.c
parentf3f483ac6310f26bd17ce5518cba14730a4d0546 (diff)
downloadqemu-09feea6cf528b3158640d6530174cf21cb579bc0.zip
qemu-09feea6cf528b3158640d6530174cf21cb579bc0.tar.gz
qemu-09feea6cf528b3158640d6530174cf21cb579bc0.tar.bz2
qemu-iotests/199: better catch postcopy time
The test aims to test _postcopy_ migration, and wants to do some write operations during postcopy time. Test considers migrate status=complete event on source as start of postcopy. This is completely wrong, completion is completion of the whole migration process. Let's instead consider destination start as start of postcopy, and use RESUME event for it. Next, as migration finish, let's use migration status=complete event on target, as such method is closer to what libvirt or another user will do, than tracking number of dirty-bitmaps. Finally, add a possibility to dump events for debug. And if set debug to True, we see, that actual postcopy period is very small relatively to the whole test duration time (~0.2 seconds to >40 seconds for me). This means, that test is very inefficient in what it supposed to do. Let's improve it in following commits. Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> Reviewed-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com> Tested-by: Eric Blake <eblake@redhat.com> Message-Id: <20200727194236.19551-4-vsementsov@virtuozzo.com> Signed-off-by: Eric Blake <eblake@redhat.com>
Diffstat (limited to 'hw/misc/arm_l2x0.c')
0 files changed, 0 insertions, 0 deletions