linux

History

Alexei Starovoitov 64a8946b44 net: filter: BPF testsuite The testsuite covers classic and internal BPF instructions. It is particularly useful for JIT compiler developers. Adds to "net" selftest target. The testsuite can be used as a set of micro-benchmarks. It measures execution time of each BPF program in nsec. This patch adds core framework. Signed-off-by: Alexei Starovoitov <ast@plumgrid.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2014-05-12 00:23:55 -04: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	tools/testing/selftests/ipc/msgque.c: handle msgget failure return correctly	2014-03-10 17:26:21 -07: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	net: filter: BPF testsuite	2014-05-12 00:23:55 -04:00
powerpc	selftests/powerpc: Import Anton's memcpy / copy_tofrom_user tests	2014-03-07 15:53:12 +11:00
ptrace	selftest: add a test case for PTRACE_PEEKSIGINFO	2013-04-30 17:04:05 -07:00
rcutorture	rcutorture: Save kvm.sh output to log	2014-02-23 09:04:44 -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.