linux

Files

Frederic Weisbecker 0bc4b0cf15 selftests: add basic posix timers selftests

Add some initial basic tests on a few posix timers interface such as
setitimer() and timer_settime().

These simply check that expiration happens in a reasonable timeframe after
expected elapsed clock time (user time, user + system time, real time,
...).

This is helpful for finding basic breakages while hacking
on this subsystem.

Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
Cc: Olivier Langlois <olivier@trillion01.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

2013-07-03 16:20:03 +02:00

breakpoints

breakpoint selftests: print failure status instead of cause make error

2012-12-17 17:15:27 -08:00

cpu-hotplug

cpu-hotplug selftests: print failure status instead of cause make error

2012-12-17 17:15:27 -08:00

efivarfs

efivars: efivarfs_valid_name() should handle pstore syntax

2013-03-06 14:46:04 +00:00

ipc

selftests: IPC message queue copy feature test

2013-01-04 16:11:45 -08:00

kcmp

tools/testing/selftests/kcmp/kcmp_test.c: print reason for failure in kcmp_test

2012-12-17 17:15:27 -08:00

memory-hotplug

mem-hotplug selftests: print failure status instead of cause make error

2012-12-17 17:15:27 -08:00

mqueue

mqueue selftests: print failure status instead of cause make error

2012-12-17 17:15:26 -08:00

net

selftests: psock_tpacket: fix status check

2013-04-29 12:26:53 -04:00

ptrace

selftest: add a test case for PTRACE_PEEKSIGINFO

2013-04-30 17:04:05 -07:00

timers

selftests: add basic posix timers selftests

2013-07-03 16:20:03 +02:00

vm selftests: print failure status instead of cause make error

2012-12-17 17:15:26 -08:00

Makefile

selftests: add basic posix timers selftests

2013-07-03 16:20:03 +02:00

README.txt

selftests: add a simple doc

2013-02-27 19:10:24 -08:00

README.txt

Linux Kernel Selftests

The kernel contains a set of "self tests" under the tools/testing/selftests/
directory. These are intended to be small unit tests to exercise individual
code paths in the kernel.

Running the selftests
=====================

To build the tests:

  $ make -C tools/testing/selftests


To run the tests:

  $ make -C tools/testing/selftests run_tests

- note that some tests will require root privileges.


To run only tests targetted for a single subsystem:

  $  make -C tools/testing/selftests TARGETS=cpu-hotplug run_tests

See the top-level tools/testing/selftests/Makefile for the list of all possible
targets.


Contributing new tests
======================

In general, the rules for for selftests are

 * Do as much as you can if you're not root;

 * Don't take too long;

 * Don't break the build on any architecture, and

 * Don't cause the top-level "make run_tests" to fail if your feature is
   unconfigured.