| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
Add a test that makes sure that the kernel does indeed not accept
infeasible densities.
|
|
|
|
| |
Try to infer current plugin if no plugin is specified.
|
|
|
|
|
|
|
|
| |
Updated APIs to support arbitrary deadlines. Added macros for implicit
deadlines.
Note: Had to tweak Makefile to support gcc version >= 4.6 (moved -lrt to the
end of the link command).
|
|
|
|
|
| |
Segmentation faults are clearly test failures;
make sure to report them accordingly.
|
|
|
|
|
| |
Under any plugin, the control page should be mappable
and writable.
|
|
|
|
|
| |
Make sure out-of-range priorities
are always rejected.
|
|
|
|
|
|
| |
PCP was only used for DPCP before
tests: add some basic tests for PCP under P-FP
|
|
|
|
|
|
|
|
|
| |
dissertation (branch bbb-diss)
I took the unchanged code but removed references
to OMLP which was and is not implemented
tests: changed so that they work for P-FP
|
|
|
|
|
|
|
| |
Since set_rt_task_param() checks for wrong budget policies,
make sure to specify a valid policy to avoid errors like the following.
litmus: real-time task 3635 rejected because unsupported budget enforcement policy specified
|
|
|
|
| |
This is useful for tests that apply to any plugin.
|
| |
|
|
|
|
|
| |
The new generic lock layer in LITMUS^RT does away with per-protocol
system calls. Change accordingly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We originally switched from make to scons because
1) our makefiles were not very good;
2) SCons promised to make maintaining the build system simpler.
Unfortunately, SCons has become more and more difficult to deal with
as we moved to supporting several architecture and cross compilation,
to the extend that we ended up re-creating make functionality in SCons.
So let's switch back to make using a "clean" Makefile.
Thanks a lot to Andrea Bastoni and Chris Kenna for feedback on
previous iterations of these patches.
|
| |
|
|
|
|
| |
Passes.
|
|
|
|
| |
All passed.
|
| |
|
|
|
|
| |
Specifically, make sure invalid pointers are rejected.
|
|
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.
|