Matt Fleming 123abd76ed efivars: efivarfs_valid_name() should handle pstore syntax 12 years ago
..
breakpoints 5a55f8bb2d breakpoint selftests: print failure status instead of cause make error 12 years ago
cpu-hotplug a58130ddc8 cpu-hotplug selftests: print failure status instead of cause make error 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 2bf1cbf1c6 tools/testing/selftests/kcmp/kcmp_test.c: print reason for failure in kcmp_test 12 years ago
memory-hotplug aabccae6e9 mem-hotplug selftests: print failure status instead of cause make error 12 years ago
mqueue 9ed1d90ed1 mqueue selftests: print failure status instead of cause make error 12 years ago
vm 000e06b01f vm selftests: print failure status instead of cause make error 12 years ago
Makefile 66a01b9659 tools/testing/selftests/Makefile: rearrange targets 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.