aboutsummaryrefslogtreecommitdiffstats
path: root/tests/fdso.c
Commit message (Collapse)AuthorAge
* Change convenience API routines.Glenn Elliott2013-03-12
| | | | | | | | | | | | | The sproadic_*() macros have become unwieldy. This patch replaces those convenience macros for global, clustered, and partitioned scheduling. A part of this API change is the explicit use of nanosecond time-values. Prior APIs have used lt_t (litmus time), which had an implied time scale of nanoseconds. /bin apps and test suite also updated to use revised API. Modifications to the test suite are mostly centered around using nanoseconds instead of milliseconds.
* uncachedev: uncache test tool.Glenn Elliott2013-03-12
| | | | | | | | | | | | | | | | | This adds the uncache test tool (bin/uncache.c). The tool can be used to test Litmus's char device driver for allocating uncacheable CPU memory. The tool runs various checks and gathers basic cache vs. main memory statistics. In the future, uncache could be extended to quantify the benefits of the L1, L2, and L3 caches, instead of treating them as a black box. Note: Uncache works best when compiled with '-O2'. While '-O2' has not been added to the Makefile, other code was updated (code in tests/ and rtspin), to compile with -O2. DEPENDS UPON LITMUS-RT PATCH 888d097deb6d1fdc0c89a4f9667fd81cf416cfc7.
* add test cases for the FMLP and SRP under GSN- and PSN-EDFBjoern B. Brandenburg2011-02-03
|
* switch to generic locking system callsBjoern B. Brandenburg2011-02-03
| | | | | The new generic lock layer in LITMUS^RT does away with per-protocol system calls. Change accordingly.
* Silence warning due to missing header file.Bjoern B. Brandenburg2010-11-09
|
* Add tests for invalid object types and od_open().Bjoern B. Brandenburg2010-02-25
|
* Introduce test framework for LITMUS^RT.Bjoern B. Brandenburg2010-02-20
This is the beginning of the LITMUS^RT testsuite. The main design goals are flexibility and ease of test writing. To create a new test, simply write a test case in any C file in the tests/ subdirectory. The buildsystem will find the test and hook it up with the testrunner. Have a look at tests/fdso.c and include/tests.h to get an idea for what tests look like. Tests can be executed with the 'runtests' tool. Each testcase is executed in a separate process in order to ensure that tests do not influence each other.