android_kernel_lenovo_1050f/tools/testing/selftests
Maurizio Porrato 8773c99499 first commit 2020-06-06 18:20:15 +01:00
..
breakpoints first commit 2020-06-06 18:20:15 +01:00
cpu-hotplug first commit 2020-06-06 18:20:15 +01:00
efivarfs first commit 2020-06-06 18:20:15 +01:00
ipc first commit 2020-06-06 18:20:15 +01:00
kcmp first commit 2020-06-06 18:20:15 +01:00
memory-hotplug first commit 2020-06-06 18:20:15 +01:00
mqueue first commit 2020-06-06 18:20:15 +01:00
net first commit 2020-06-06 18:20:15 +01:00
ptrace first commit 2020-06-06 18:20:15 +01:00
vm first commit 2020-06-06 18:20:15 +01:00
Makefile first commit 2020-06-06 18:20:15 +01:00
README.txt first commit 2020-06-06 18:20:15 +01: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.