Shuah Khan
e84f1ab33c
tools/testing/selftests/ipc/msgque.c: improve error handling when not running as root
|
há 11 anos atrás | |
|---|---|---|
| .. | ||
| breakpoints | há 13 anos atrás | |
| cpu-hotplug | há 11 anos atrás | |
| efivarfs | há 13 anos atrás | |
| ipc | há 11 anos atrás | |
| kcmp | há 12 anos atrás | |
| memory-hotplug | há 11 anos atrás | |
| mqueue | há 13 anos atrás | |
| net | há 11 anos atrás | |
| powerpc | há 11 anos atrás | |
| ptrace | há 12 anos atrás | |
| rcutorture | há 11 anos atrás | |
| sysctl | há 11 anos atrás | |
| timers | há 12 anos atrás | |
| user | há 12 anos atrás | |
| vm | há 12 anos atrás | |
| Makefile | há 11 anos atrás | |
| README.txt | há 13 anos atrás | |
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.
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.