Michael Ellerman cb96143def selftests: Add test of PMU instruction counting on powerpc 12 years ago
..
breakpoints 5a55f8bb2d breakpoint selftests: print failure status instead of cause make error 12 years ago
cpu-hotplug 9307c29524 tools/testing/selftests: don't assume the x bit is set on scripts 12 years ago
efivarfs 123abd76ed efivars: efivarfs_valid_name() should handle pstore syntax 12 years ago
ipc 3a665531a3 selftests: IPC message queue copy feature test 12 years ago
kcmp 94d090013e selftests: add .gitignore for kcmp 12 years ago
memory-hotplug 9307c29524 tools/testing/selftests: don't assume the x bit is set on scripts 12 years ago
mqueue 9ed1d90ed1 mqueue selftests: print failure status instead of cause make error 12 years ago
net 37beae65fa tools: selftests: psock_tpacket: get rid of macro wrappers 12 years ago
powerpc cb96143def selftests: Add test of PMU instruction counting on powerpc 12 years ago
ptrace 17afab1de4 selftest: add a test case for PTRACE_PEEKSIGINFO 12 years ago
timers 0bc4b0cf15 selftests: add basic posix timers selftests 12 years ago
vm c7fed9cf61 selftests: add .gitignore for vm 12 years ago
Makefile 0e56dacdda selftests: Add infrastructure for powerpc selftests 12 years ago
README.txt 80d0342859 selftests: add a simple doc 12 years ago

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.