KVM: selftests: memslot_perf_test: increase guest sync timeout
authorMaxim Levitsky <mlevitsk@redhat.com>
Fri, 4 Oct 2024 22:01:53 +0000 (18:01 -0400)
committerSean Christopherson <seanjc@google.com>
Tue, 5 Nov 2024 05:04:10 +0000 (21:04 -0800)
When memslot_perf_test is run nested, first iteration of test_memslot_rw_loop
testcase, sometimes takes more than 2 seconds due to build of shadow page tables.

Following iterations are fast.

To be on the safe side, bump the timeout to 10 seconds.

Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
Tested-by: Liam Merwick <liam.merwick@oracle.com>
Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
Link: https://lore.kernel.org/r/20241004220153.287459-1-mlevitsk@redhat.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
tools/testing/selftests/kvm/memslot_perf_test.c

index 989ffe0d047f19e1ed12b20608d551e952f3f460..e3711beff7f314920c45998dff2be07c413052cb 100644 (file)
@@ -417,7 +417,7 @@ static bool _guest_should_exit(void)
  */
 static noinline void host_perform_sync(struct sync_area *sync)
 {
-       alarm(2);
+       alarm(10);
 
        atomic_store_explicit(&sync->sync_flag, true, memory_order_release);
        while (atomic_load_explicit(&sync->sync_flag, memory_order_acquire))