* [PATCH] KVM Test: time_drift_with_stop: Wait a few seconds after the continue
@ 2010-07-29 3:38 Amos Kong
0 siblings, 0 replies; only message in thread
From: Amos Kong @ 2010-07-29 3:38 UTC (permalink / raw)
To: lmr; +Cc: autotest, kvm
Except for kvm-clock, we need to wait a few seconds to let the interrupt
lost during the stop to be reinjected. So sleep for 30 seconds ( could
be configurated throug configuration file).
Signed-off-by: Jason Wang <jasowang@redhat.com>
Signed-off-by: Amos Kong <akong@redhat.com>
---
0 files changed, 0 insertions(+), 0 deletions(-)
diff --git a/client/tests/kvm/tests/timedrift_with_stop.py b/client/tests/kvm/tests/timedrift_with_stop.py
index fe98571..3473276 100644
--- a/client/tests/kvm/tests/timedrift_with_stop.py
+++ b/client/tests/kvm/tests/timedrift_with_stop.py
@@ -20,6 +20,7 @@ def run_timedrift_with_stop(test, params, env):
@param env: Dictionary with the test environment.
"""
login_timeout = int(params.get("login_timeout", 360))
+ sleep_time = int(params.get("sleep_time", 30))
vm = kvm_test_utils.get_living_vm(env, params.get("main_vm"))
session = kvm_test_utils.wait_for_login(vm, timeout=login_timeout)
@@ -54,6 +55,10 @@ def run_timedrift_with_stop(test, params, env):
time.sleep(stop_time)
vm.monitor.cmd("cont")
+ # Sleep for a while to wait the interrupt to be reinjected
+ logging.info("Waiting for the interrupt to be reinjected ...")
+ time.sleep(sleep_time)
+
# Get time after current iteration
(ht1_, gt1_) = kvm_test_utils.get_time(session, time_command,
time_filter_re, time_format)
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2010-07-29 3:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-07-29 3:38 [PATCH] KVM Test: time_drift_with_stop: Wait a few seconds after the continue Amos Kong
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox