diff options
| author | Hyman Huang <yong.huang@smartx.com> | 2023-11-01 22:04:06 +0800 |
|---|---|---|
| committer | Juan Quintela <quintela@redhat.com> | 2023-11-03 07:48:25 +0100 |
| commit | 17257b90be4f51dd3040ca2e472201407b2327c4 (patch) | |
| tree | 7ec788e4f74635987fab4f4347357a2a010b2bc3 /tests/qtest/xlnx-versal-trng-test.c | |
| parent | 78a7ef15804c0c0a886fcf9f12e5464f8eddd20c (diff) | |
| download | qemu-17257b90be4f51dd3040ca2e472201407b2327c4.zip qemu-17257b90be4f51dd3040ca2e472201407b2327c4.tar.gz qemu-17257b90be4f51dd3040ca2e472201407b2327c4.tar.bz2 | |
tests: Add migration dirty-limit capability test
Add migration dirty-limit capability test if kernel support
dirty ring.
Migration dirty-limit capability introduce dirty limit
capability, two parameters: x-vcpu-dirty-limit-period and
vcpu-dirty-limit are introduced to implement the live
migration with dirty limit.
The test case does the following things:
1. start src, dst vm and enable dirty-limit capability
2. start migrate and set cancel it to check if dirty limit
stop working.
3. restart dst vm
4. start migrate and enable dirty-limit capability
5. check if migration satisfy the convergence condition
during pre-switchover phase.
Note that this test case involves many passes, so it runs
in slow mode only.
Signed-off-by: Hyman Huang <yong.huang@smartx.com>
Acked-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Message-ID: <e55a302df9da7dbc00ad825f47f57c1a756d303e.1698847223.git.yong.huang@smartx.com>
Diffstat (limited to 'tests/qtest/xlnx-versal-trng-test.c')
0 files changed, 0 insertions, 0 deletions