linux

History

Paul E. McKenney c7e8240db1 rcutorture: Print grace-period performance statistics Sometime problems can manifest themselves as unusually slow grace periods. This commit therefore prints the number of rcutorture updates during the test and the number per second. These statistics are harvested from the config.out and qemu-cmd files, and are silently omitted if these files are not available, as would be the case if there was a build failure or a boot-time hang. Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Reviewed-by: Josh Triplett <josh@joshtriplett.org>		2014-02-18 12:24:22 -08: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	tools: selftests: psock_tpacket: get rid of macro wrappers	2013-07-02 00:23:57 -07:00
powerpc	selftests: Add test of PMU instruction counting on powerpc	2013-08-14 14:57:10 +10:00
ptrace	selftest: add a test case for PTRACE_PEEKSIGINFO	2013-04-30 17:04:05 -07:00
rcutorture	rcutorture: Print grace-period performance statistics	2014-02-18 12:24:22 -08:00
timers	tools/testing/selftests: fix uninitialized variable	2013-10-16 21:35:53 -07:00
user	test: check copy_to/from_user boundary validation	2014-01-23 16:36:57 -08:00
vm	selftests: add .gitignore for vm	2013-07-03 16:08:07 -07:00
Makefile	test: check copy_to/from_user boundary validation	2014-01-23 16:36:57 -08: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.