1
0
This repository has been archived on 2024-07-22. You can view files and clone it, but cannot push or open issues or pull requests.
TP-Link_Archer-XR500v/EN7526G_3.18Kernel_SDK/linux-3.18.21/tools/testing/selftests
2024-07-22 01:58:46 -03:00
..
breakpoints Add gpl 2024-07-22 01:58:46 -03:00
cpu-hotplug Add gpl 2024-07-22 01:58:46 -03:00
efivarfs Add gpl 2024-07-22 01:58:46 -03:00
firmware Add gpl 2024-07-22 01:58:46 -03:00
ftrace Add gpl 2024-07-22 01:58:46 -03:00
ipc Add gpl 2024-07-22 01:58:46 -03:00
kcmp Add gpl 2024-07-22 01:58:46 -03:00
memfd Add gpl 2024-07-22 01:58:46 -03:00
memory-hotplug Add gpl 2024-07-22 01:58:46 -03:00
mount Add gpl 2024-07-22 01:58:46 -03:00
mqueue Add gpl 2024-07-22 01:58:46 -03:00
net Add gpl 2024-07-22 01:58:46 -03:00
powerpc Add gpl 2024-07-22 01:58:46 -03:00
ptrace Add gpl 2024-07-22 01:58:46 -03:00
rcutorture Add gpl 2024-07-22 01:58:46 -03:00
sysctl Add gpl 2024-07-22 01:58:46 -03:00
timers Add gpl 2024-07-22 01:58:46 -03:00
user Add gpl 2024-07-22 01:58:46 -03:00
vm Add gpl 2024-07-22 01:58:46 -03:00
Makefile Add gpl 2024-07-22 01:58:46 -03:00
README.txt Add gpl 2024-07-22 01:58:46 -03:00

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.