[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260102183039.496725-1-yosry.ahmed@linux.dev>
Date: Fri, 2 Jan 2026 18:30:39 +0000
From: Yosry Ahmed <yosry.ahmed@...ux.dev>
To: Sean Christopherson <seanjc@...gle.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Andrew Jones <andrew.jones@...ux.dev>
Cc: kvm@...r.kernel.org,
linux-kernel@...r.kernel.org,
Yosry Ahmed <yosry.ahmed@...ux.dev>
Subject: [kvm-unit-tests PATCH] x86: Increase the timeout for vmx_pf_{vpid/no_vpid/invvpid}_test
When running the tests on some older CPUs (e.g. Skylake) on a kernel
with some debug config options enabled (e.g. CONFIG_DEBUG_VM,
CONFIG_PROVE_LOCKING, ..), the tests timeout. In this specific setup,
the tests take between 4 and 5 minutes, so pump the timeout from 4 to 6
minutes.
Signed-off-by: Yosry Ahmed <yosry.ahmed@...ux.dev>
---
x86/unittests.cfg | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/x86/unittests.cfg b/x86/unittests.cfg
index 522318d32bf6..bb2b9f033b11 100644
--- a/x86/unittests.cfg
+++ b/x86/unittests.cfg
@@ -427,7 +427,7 @@ test_args = "vmx_pf_vpid_test"
qemu_params = -cpu max,+vmx
arch = x86_64
groups = vmx nested_exception nodefault
-timeout = 240
+timeout = 360
[vmx_pf_invvpid_test]
file = vmx.flat
@@ -435,7 +435,7 @@ test_args = "vmx_pf_invvpid_test"
qemu_params = -cpu max,+vmx
arch = x86_64
groups = vmx nested_exception nodefault
-timeout = 240
+timeout = 360
[vmx_pf_no_vpid_test]
file = vmx.flat
@@ -443,7 +443,7 @@ test_args = "vmx_pf_no_vpid_test"
qemu_params = -cpu max,+vmx
arch = x86_64
groups = vmx nested_exception nodefault
-timeout = 240
+timeout = 360
[vmx_pf_exception_test_reduced_maxphyaddr]
file = vmx.flat
--
2.52.0.351.gbe84eed79e-goog
Powered by blists - more mailing lists