David Herrmann 525d9c960e selftests: add memfd/sealing page-pinning tests 10 years ago
..
breakpoints d950ec9b4d Add initial Stable Samsung msm8974 family kernel 5 years ago
cpu-hotplug 4a1aeace23 tools: selftests - create a separate hotplug target for full range test 2 years ago
efivarfs 2518612ced selftests: add tests for efivarfs 2 years ago
epoll 6536f276da epoll: support for disabling items, and a self-test app 2 years ago
memfd 525d9c960e selftests: add memfd/sealing page-pinning tests 2 years ago
memory-hotplug 4a1aeace23 tools: selftests - create a separate hotplug target for full range test 2 years ago
mqueue fe27460192 selftests: add mq_open_tests 2 years ago
net be7e0c4a7c net: Move selftests to common net/ subdirectory. 2 years ago
net-socket be7e0c4a7c net: Move selftests to common net/ subdirectory. 2 years ago
powerpc e58c82d68f selftests: Add infrastructure for powerpc selftests 2 years ago
ptrace ab1b647612 selftest: add a test case for PTRACE_PEEKSIGINFO 2 years ago
sysctl 23cebc1edf tools/testing/selftests/sysctl: validate sysctl_writes_strict 2 years ago
timers 5c90d936cb selftests: add basic posix timers selftests 2 years ago
user 2dacfb4b11 test: check copy_to/from_user boundary validation 2 years ago
vm d950ec9b4d Add initial Stable Samsung msm8974 family kernel 5 years ago
Makefile 88eec435f4 selftests: add memfd_create() + sealing tests 2 years ago
README.txt 4a1aeace23 tools: selftests - create a separate hotplug target for full range test 2 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.

On some systems, hot-plug tests could hang forever waiting for cpu and
memory to be ready to be offlined. A special hot-plug target is created
to run full range of hot-plug tests. In default mode, hot-plug tests run
in safe mode with a limited scope. In limited mode, cpu-hotplug test is
run on a single cpu as opposed to all hotplug capable cpus, and memory
hotplug test is run on 2% of hotplug capable memory instead of 10%.

Running the selftests (hotplug tests are run in limited mode)
=============================================================

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 targeted for a single subsystem: (including
hotplug targets in limited mode)

$ 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.

Running the full range hotplug selftests
========================================

To build the tests:

$ make -C tools/testing/selftests hotplug

To run the tests:

$ make -C tools/testing/selftests run_hotplug

- note that some tests will require root privileges.

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.