linux-stable.git/tools/testing/selftests/timers, branch linux-4.3.y

Merge tag 'linux-kselftest-4.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest

2015-06-29T16:11:10+00:00

Pull kselftest update from Shuah Khan:
 "This update adds two new test suites: futex and seccomp.

  In addition, it includes fixes for bugs in timers, other tests, and
  compile framework.  It introduces new quicktest feature to enable
  users to choose to run tests that complete in a short time"

* tag 'linux-kselftest-4.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest:
  selftests: add quicktest support
  selftests: add seccomp suite
  selftest, x86: fix incorrect comment
  tools selftests: Fix 'clean' target with make 3.81
  selftests/futex: Add .gitignore
  kselftest: Add exit code defines
  selftests: Add futex tests to the top-level Makefile
  selftests/futex: Increment ksft pass and fail counters
  selftests/futex: Update Makefile to use lib.mk
  selftests: Add futex functional tests
  kselftests: timers: Check _ALARM clockids are supported before suspending
  kselftests: timers: Ease alarmtimer-suspend unreasonable latency value
  kselftests: timers: Increase delay between suspends in alarmtimer-suspend
  selftests/exec: do not install subdir as it is already created
  selftests/ftrace: install test.d
  selftests: copy TEST_DIRS to INSTALL_PATH
  Test compaction of mlocked memory
  selftests/mount: output WARN messages when mount test skipped
  selftests/timers: Make git ignore all binaries in timers test suite

selftest: Timers: Avoid signal deadlock in leap-a-day

2015-06-18T13:28:14+00:00

In 0c4a5fc95b1df (Add leap-second timer edge testing to
leap-a-day.c), we added a timer to the test which checks to make
sure timers near the leapsecond edge behave correctly.

However, the output generated from the timer uses ctime_r, which
isn't async-signal safe, and should that signal land while the
main test is using ctime_r to print its output, its possible for
the test to deadlock on glibc internal locks.

Thus this patch reworks the output to avoid using ctime_r in
the signal handler.

Signed-off-by: John Stultz 
Cc: Prarit Bhargava 
Cc: Daniel Bristot de Oliveira 
Cc: Richard Cochran 
Cc: Jan Kara 
Cc: Jiri Bohac 
Cc: Shuah Khan 
Cc: Ingo Molnar 
Link: http://lkml.kernel.org/r/1434565003-3386-1-git-send-email-john.stultz@linaro.org
Signed-off-by: Thomas Gleixner

selftests: timers: Add leap-second timer edge testing to leap-a-day.c

2015-06-12T09:15:50+00:00

Prarit reported an issue w/ timers around the leapsecond, where a
timer set for Midnight UTC (00:00:00) might fire a second early right
before the leapsecond (23:59:60 - though it appears as a repeated
23:59:59) is applied.

So I've updated the leap-a-day.c test to integrate a similar test,
where we set a timer and check if it triggers at the right time, and
if the ntp state transition is managed properly.

Reported-by: Daniel Bristot de Oliveira 
Reported-by: Prarit Bhargava 
Signed-off-by: John Stultz 
Cc: Richard Cochran 
Cc: Jan Kara 
Cc: Jiri Bohac 
Cc: Shuah Khan 
Cc: Ingo Molnar 
Link: http://lkml.kernel.org/r/1434063297-28657-6-git-send-email-john.stultz@linaro.org
Signed-off-by: Thomas Gleixner

kselftests: timers: Check _ALARM clockids are supported before suspending

2015-05-26T21:58:07+00:00

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 
Cc: Prarit Bhargava 
Cc: Thomas Gleixner 
Cc: Richard Cochran 
Signed-off-by: John Stultz 
Signed-off-by: Shuah Khan

kselftests: timers: Ease alarmtimer-suspend unreasonable latency value

2015-05-26T21:58:07+00:00

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 
Cc: Prarit Bhargava 
Cc: Thomas Gleixner 
Cc: Richard Cochran 
Signed-off-by: John Stultz 
Signed-off-by: Shuah Khan

kselftests: timers: Increase delay between suspends in alarmtimer-suspend

2015-05-26T21:58:07+00:00

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 
Cc: Prarit Bhargava 
Cc: Thomas Gleixner 
Cc: Richard Cochran 
Signed-off-by: John Stultz 
Signed-off-by: Shuah Khan

selftests/timers: Make git ignore all binaries in timers test suite

2015-05-26T21:58:06+00:00

This patch includes the timers test binaries into the .gitignore
file listing in their respective directories. This will make sure
that git ignores all of these test binaries when displaying status.

Signed-off-by: Zhang Zhen 
Signed-off-by: Shuah Khan

kselftests: timers: Make set-timer-lat fail more gracefully for !CAP_WAKE_ALARM

2015-04-02T16:32:33+00:00

The set-timer-lat test fails when testing CLOCK_BOOTTIME_ALARM
or CLOCK_REALTIME_ALARM when the user isn't running as root or
with CAP_WAKE_ALARM.

So this patch improves the error checking so we report the
issue more clearly and continue rather then reporting a failure.

Cc: Shuah Khan 
Cc: Prarit Bhargava 
Cc: Thomas Gleixner 
Cc: Richard Cochran 
Signed-off-by: John Stultz 
Signed-off-by: Shuah Khan

kselftests: timers: Reduce default runtime on inconsistency-check and set-timer-lat

2015-03-31T19:44:32+00:00

For the default run_timers target, the timers tests takes the
majority of kselftests runtime.

So this patch reduces the default runtime for inconsistentcy-check
and set-timer-lat, which reduced the runtime almost in half.

Before:	11m48.629s
After:	6m47.723s

Cc: Shuah Khan 
Cc: Prarit Bhargava 
Cc: Thomas Gleixner 
Cc: Richard Cochran 
Signed-off-by: John Stultz 
Signed-off-by: Shuah Khan

tools, update rtctest.c to verify passage of time

2015-03-25T04:02:59+00:00

rtctest.c checks to see if PIE is functioning by testing if 20 interrupts occur
at rates from 2HZ to 64HZ.  While this check is good, it does not check to
see if the correct amount of time has actually passed.  This misses
situations where the RTC may be operating at a higher or lower frequency
than expected.

This patch introduces a simple check to verify if the time passed is
less than 10% of what was programmed into the RTC.

Signed-off-by: Prarit Bhargava 
Acked-by: John Stultz 
Cc: corbet@lwn.net
Cc: rtc-linux@googlegroups.com
Cc: linux-doc@vger.kernel.org
Cc: a.zummo@towertech.it
Cc: prarit@redhat.com
Cc: john.stultz@linaro.org
Cc: shuahkh@osg.samsung.com
Signed-off-by: Shuah Khan