~ [ source navigation ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/tools/testing/selftests/futex/

Version: ~ [ linux-5.8 ] ~ [ linux-5.7.14 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.57 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.138 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.193 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.232 ] ~ [ linux-4.8.17 ] ~ [ linux-4.7.10 ] ~ [ linux-4.6.7 ] ~ [ linux-4.5.7 ] ~ [ linux-4.4.232 ] ~ [ linux-4.3.6 ] ~ [ linux-4.2.8 ] ~ [ linux-4.1.52 ] ~ [ linux-4.0.9 ] ~ [ linux-3.19.8 ] ~ [ linux-3.18.140 ] ~ [ linux-3.17.8 ] ~ [ linux-3.16.85 ] ~ [ linux-3.15.10 ] ~ [ linux-3.14.79 ] ~ [ linux-3.13.11 ] ~ [ linux-3.12.74 ] ~ [ linux-3.11.10 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.5 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Name Size Last modified (GMT) Description
Back Parent directory 2016-06-14 12:30:55
Folder functional/ 2016-06-14 12:30:55
Folder include/ 2016-06-14 12:30:55
File Makefile 550 bytes 2016-06-14 12:30:55
File README 2639 bytes 2016-06-14 12:30:55
File run.sh 974 bytes 2016-06-14 12:30:55

  1 Futex Test
  2 ==========
  3 Futex Test is intended to thoroughly test the Linux kernel futex system call
  4 API.
  5 
  6 Functional tests shall test the documented behavior of the futex operation
  7 code under test. This includes checking for proper behavior under normal use,
  8 odd corner cases, regression tests, and abject abuse and misuse.
  9 
 10 Futextest will also provide example implementation of mutual exclusion
 11 primitives. These can be used as is in user applications or can serve as
 12 examples for system libraries. These will likely be added to either a new lib/
 13 directory or purely as header files under include/, I'm leaning toward the
 14 latter.
 15 
 16 Quick Start
 17 -----------
 18 # make
 19 # ./run.sh
 20 
 21 Design and Implementation Goals
 22 -------------------------------
 23 o Tests should be as self contained as is practical so as to facilitate sharing
 24   the individual tests on mailing list discussions and bug reports.
 25 o The build system shall remain as simple as possible, avoiding any archive or
 26   shared object building and linking.
 27 o Where possible, any helper functions or other package-wide code shall be
 28   implemented in header files, avoiding the need to compile intermediate object
 29   files.
 30 o External dependencies shall remain as minimal as possible. Currently gcc
 31   and glibc are the only dependencies.
 32 o Tests return 0 for success and < 0 for failure.
 33 
 34 Output Formatting
 35 -----------------
 36 Test output shall be easily parsable by both human and machine. Title and
 37 results are printed to stdout, while intermediate ERROR or FAIL messages are
 38 sent to stderr. Tests shall support the -c option to print PASS, FAIL, and
 39 ERROR strings in color for easy visual parsing. Output shall conform to the
 40 following format:
 41 
 42 test_name: Description of the test
 43         Arguments: arg1=val1 #units specified for clarity where appropriate
 44         ERROR: Description of unexpected error
 45          FAIL: Reason for test failure
 46         # FIXME: Perhaps an " INFO: informational message" option would be
 47         #        useful here. Using -v to toggle it them on and off, as with -c.
 48         # there may be multiple ERROR or FAIL messages
 49 Result: (PASS|FAIL|ERROR)
 50 
 51 Naming
 52 ------
 53 o FIXME: decide on a sane test naming scheme.  Currently the tests are named
 54   based on the primary futex operation they test. Eventually this will become a
 55   problem as we intend to write multiple tests which collide in this namespace.
 56   Perhaps something like "wait-wake-1" "wait-wake-2" is adequate, leaving the
 57   detailed description in the test source and the output.
 58 
 59 Coding Style
 60 ------------
 61 o The Futex Test project adheres to the coding standards set forth by Linux
 62   kernel as defined in the Linux source Documentation/CodingStyle.

~ [ source navigation ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | Wiki (Japanese) | Wiki (English) | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

osdn.jp