kernel-ark

History

Andrew Morton 9307c29524 tools/testing/selftests: don't assume the x bit is set on scripts The x bit can easily get lost (patch(1) loses it, for example). Reported-by: Ramkumar Ramachandra <artagnon@gmail.com> Cc: Dave Young <dyoung@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2013-07-03 16:08:07 -07:00
..
breakpoints	breakpoint selftests: print failure status instead of cause make error	2012-12-17 17:15:27 -08:00
cpu-hotplug	tools/testing/selftests: don't assume the x bit is set on scripts	2013-07-03 16:08:07 -07:00
efivarfs	efivars: efivarfs_valid_name() should handle pstore syntax	2013-03-06 14:46:04 +00:00
ipc	selftests: IPC message queue copy feature test	2013-01-04 16:11:45 -08:00
kcmp	selftests: add .gitignore for kcmp	2013-07-03 16:08:07 -07:00
memory-hotplug	tools/testing/selftests: don't assume the x bit is set on scripts	2013-07-03 16:08:07 -07:00
mqueue	mqueue selftests: print failure status instead of cause make error	2012-12-17 17:15:26 -08:00
net	selftests: psock_tpacket: fix status check	2013-04-29 12:26:53 -04:00
ptrace	selftest: add a test case for PTRACE_PEEKSIGINFO	2013-04-30 17:04:05 -07:00
vm	selftests: add .gitignore for vm	2013-07-03 16:08:07 -07:00
Makefile	revert "selftest: add simple test for soft-dirty bit"	2013-05-24 16:22:52 -07:00
README.txt	selftests: add a simple doc	2013-02-27 19:10:24 -08:00

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.