liblitmus.git/include, branch 2010.2 [ARCHIVE] The userspace library for LITMUS^RT 2010. Now on GitHub. Support budget enforcement policies. Allows tasks to specify 2010-05-20T18:17:58+00:00 Glenn Elliott gelliott@koruna.cs.unc.edu 2010-05-20T18:17:58+00:00 e9c900fae35e4e4730469e189ff17bf30518346a how their execution budgets should be enforced: NO_ENFORCEMENT, QUANTUM_ENFORCEMENT, and PRECISE_ENFORCEMENT (unsupported). NOTE: Users of NO_ENFORCEMENT must call sleep_next_period() at the end of every job to signal to the kernel that its job is complete. 
how their execution budgets should be enforced: NO_ENFORCEMENT,
QUANTUM_ENFORCEMENT, and PRECISE_ENFORCEMENT (unsupported).

NOTE: Users of NO_ENFORCEMENT must call sleep_next_period() at the
end of every job to signal to the kernel that its job is complete.
Add atomic operations on x86_64 2010-04-19T23:28:07+00:00 Andrea Bastoni bastoni@cs.unc.edu 2010-04-19T23:28:07+00:00 09740315d4b914203c25c56e8f8909b4fae7b32d 






Add cli() and sti() wrappers... use with care...
2010-04-13T03:31:52+00:00

Andrea Bastoni
bastoni@cs.unc.edu

2010-04-13T03:31:52+00:00

60dd9a5ff55f32cf34041218818307a4c7b5d78a












Add get_control_page() library function
2010-04-13T03:30:36+00:00

Andrea Bastoni
bastoni@cs.unc.edu

2010-04-13T03:30:36+00:00

05b2ec2ab620b102a2d2fb92dac95ddbc1e09143












Remove prototype for non-existing system call.
2010-02-26T14:18:05+00:00

Bjoern B. Brandenburg
bbb@cs.unc.edu

2010-02-26T14:18:05+00:00

fb807645f92cdb0239bc831746d8a1bcc04ce1bb

This syscall hasn't been around since Fall 2007... The RTCSA'08 paper
details how we are doing it now.





This syscall hasn't been around since Fall 2007... The RTCSA'08 paper
details how we are doing it now.







Provide additional information on test failures.
2010-02-26T00:39:43+00:00

Bjoern B. Brandenburg
bbb@cs.unc.edu

2010-02-26T00:39:43+00:00

374341e3169b1741ce8c9404d096c620c4c15c92












Merge branch 'tests'
2010-02-25T23:16:52+00:00

Bjoern B. Brandenburg
bbb@cs.unc.edu

2010-02-25T23:16:52+00:00

f534210a79a04e1e9aeec7dcb8e900d933b8bae2












Added protections to litmus.h to prevent name mangling when used
2010-02-22T14:28:48+00:00

Glenn Elliott
gelliott@koruna.cs.unc.edu

2010-02-22T14:28:48+00:00

8026e36c2901691bde793f85f7a0f8ca6e9c44dc

in C++ code.





in C++ code.







Introduce test framework for LITMUS^RT.
2010-02-21T02:48:29+00:00

Bjoern B. Brandenburg
bbb@cs.unc.edu

2010-02-21T02:48:29+00:00

f3d21c128e5b40acd1f15e3ddcd7fd54ca3a9bed

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.





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.







Re-implement non-preemptive section support.
2010-02-04T02:55:58+00:00

Bjoern B. Brandenburg
bbb@cs.unc.edu

2010-02-03T14:51:57+00:00

8a1912c177e978574250cf80f8a50edf7424b158

Layered on top of the LITMUS control page.





Layered on top of the LITMUS control page.