BMC/Intel-BMC/linux.git/tools/testing/selftests/timers/alarmtimer-suspend.c, branch devIntel OpenBMC Linux kernel source tree (mirror)https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev2015-05-26T21:58:07+00:00kselftests: timers: Check _ALARM clockids are supported before suspending2015-05-26T21:58:07+00:00John Stultzjohn.stultz@linaro.org2015-05-13T22:13:05+00:00urn:sha1:61171d0407b537eff299aea2388773b6c760e6eb
It was reported that the alarmtimer-suspend test hangs on older
systems that don't support _ALARM clockids.
This is due to the fact that we don't check if the timer_create
fails, and thus when we suspend, the system will not programatically
resume.
Fix this by checking the timer_create call for errors.
Cc: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Richard Cochran <richardcochran@gmail.com>
Signed-off-by: John Stultz <john.stultz@linaro.org>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
kselftests: timers: Ease alarmtimer-suspend unreasonable latency value2015-05-26T21:58:07+00:00John Stultzjohn.stultz@linaro.org2015-05-13T22:13:04+00:00urn:sha1:acd5705d2d17a229b1aa0e549951ec66164b9379
On the hardware I have, resume latency from an alarm is often
2-3 seconds (with a fair amount of variability due to the RTC's
single second granularity). Having four seconds be the pass/fail
bar is maybe a little too tight, so extend this to 5 seconds.
Cc: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Richard Cochran <richardcochran@gmail.com>
Signed-off-by: John Stultz <john.stultz@linaro.org>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
kselftests: timers: Increase delay between suspends in alarmtimer-suspend2015-05-26T21:58:07+00:00John Stultzjohn.stultz@linaro.org2015-05-13T22:13:03+00:00urn:sha1:859b1bebe1e0e2e1fdfec77b019b9d7c27588e02
When testing on some hardware, waiting only a second before
re-triggering suspend can keep TCP connections from re-establishing
which after a number of cycles can cause TCP connections to close
while the test is running.
So extend the delay between suspend calls to 3 seconds to let
the connections stay alive.
Cc: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Richard Cochran <richardcochran@gmail.com>
Signed-off-by: John Stultz <john.stultz@linaro.org>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
selftests/timers: Add alarmtimer-suspend test from timetests suite2015-03-12T19:22:14+00:00John Stultzjohn.stultz@linaro.org2015-03-12T00:40:07+00:00urn:sha1:b7bb8442fa902272ffe937a226829c9be7bfb14b
This adds the alarmtimer-suspend test from the timetests suite,
which tests that the alarmtimers wake the system up from suspend
shortly after the time they were set to fire.
Cc: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Richard Cochran <richardcochran@gmail.com>
Signed-off-by: John Stultz <john.stultz@linaro.org>
Tested-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>