forked from Minki/linux
ddddda9bc4
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%. In addition to the above change, cpu-hotplug is chnged to change processor affinity to cpu 0 so it doesn't impact itself while the test runs. Signed-off-by: Shuah Khan <shuah.kh@samsung.com> Cc: Kees Cook <keescook@chromium.org> Cc: Michael Ellerman <michael@ellerman.id.au> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org> Cc: Frederic Weisbecker <fweisbec@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
62 lines
1.7 KiB
Plaintext
62 lines
1.7 KiB
Plaintext
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.
|