You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
kernel_samsung_sm7125/tools/testing/selftests
Linus Torvalds 77e40aae76 Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace 11 years ago
..
breakpoints
cpu-hotplug tools: selftests - create a separate hotplug target for full range test 11 years ago
efivarfs
firmware test: add firmware_class loader test 11 years ago
ipc tools/testing/selftests/ipc/msgque.c: improve error handling when not running as root 11 years ago
kcmp tools: fix kcmp_test compile warnings 11 years ago
memfd selftests: add memfd/sealing page-pinning tests 11 years ago
memory-hotplug tools: selftests - create a separate hotplug target for full range test 11 years ago
mount mnt: Add tests for unprivileged remount cases that have found to be faulty 11 years ago
mqueue tools: Fix mqueue Makefile compile linking order 11 years ago
net
powerpc selftests/powerpc: Add test of per-event excludes 11 years ago
ptrace tools/testing/selftests/ptrace/peeksiginfo.c: add PAGE_SIZE definition 11 years ago
rcutorture Merge branches 'doc.2014.07.08a', 'fixes.2014.07.09a', 'maintainers.2014.07.08b', 'nocbs.2014.07.07a' and 'torture.2014.07.07a' into HEAD 11 years ago
sysctl
timers
user
vm
Makefile Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace 11 years ago
README.txt tools: selftests - create a separate hotplug target for full range test 11 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.