android_kernel_motorola_sm6225

asgardius/android_kernel_motorola_sm6225

History

Willem de Bruijn 98e821a2a9 net: fix psock_fanout on sparc64 The packetsocket fanout test uses a packet ring. Use TPACKET_V2 instead of TPACKET_V1 to work around a known 32/64 bit issue in the older ring that manifests on sparc64. Signed-off-by: Willem de Bruijn <willemb@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2013-03-21 14:31:36 -04:00
..
breakpoints	breakpoint selftests: print failure status instead of cause make error	2012-12-17 17:15:27 -08:00
cpu-hotplug	cpu-hotplug selftests: print failure status instead of cause make error	2012-12-17 17:15:27 -08: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	tools/testing/selftests/kcmp/kcmp_test.c: print reason for failure in kcmp_test	2012-12-17 17:15:27 -08:00
memory-hotplug	mem-hotplug selftests: print failure status instead of cause make error	2012-12-17 17:15:27 -08:00
mqueue	mqueue selftests: print failure status instead of cause make error	2012-12-17 17:15:26 -08:00
net	net: fix psock_fanout on sparc64	2013-03-21 14:31:36 -04:00
vm	vm selftests: print failure status instead of cause make error	2012-12-17 17:15:26 -08:00
Makefile	net: Move selftests to common net/ subdirectory.	2013-03-20 15:07:56 -04: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.