liblitmus.git/src, branch 2012.1 [ARCHIVE] The userspace library for LITMUS^RT 2010. Now on GitHub. Switch to new np-section protocol. 2011-11-24T19:48:23+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2011-07-28T05:16:04+00:00 4d4ba58fca7753c1bbe56d43e7977f2a9601e772 Everything is in one 32-bit word now. 
Everything is in one 32-bit word now.
update headers 2011-11-24T19:48:23+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2011-07-25T19:35:23+00:00 ecf0549adc8b86c9daeee9eb4cd186fdec2aa21b we need uint64_t in litmus.h 
we need uint64_t in litmus.h
switch to generic locking system calls 2011-02-03T22:40:16+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2011-01-29T19:53:21+00:00 c4128b99e1206d03d15c5d2e1b6af164bf261c40 The new generic lock layer in LITMUS^RT does away with per-protocol system calls. Change accordingly. 
The new generic lock layer in LITMUS^RT does away with per-protocol
system calls. Change accordingly.
Export wctime() and cputime() from rtspin to library clients 2011-02-03T22:40:16+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2011-01-30T17:18:26+00:00 86b445e39c3c7eed076b01795b17f34481517288 The timing functions are quite handy when building benchmark tasks. Avoid copy&paste reuse by making them available via the library. 
The timing functions are quite handy when building benchmark tasks.
Avoid copy&paste reuse by making them available via the library.
remove asm/atomic.h 2010-11-09T21:35:33+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-11-06T23:26:02+00:00 5e40fcc568a204ce8b96f734a71402d0ca52e076 For historic resons, we carry old atomic operations support in liblitmus. This is no longer useful: 1) There is actually no client for these calls in liblitmus. 2) There is now a standard gcc API for this purpose. http://gcc.gnu.org/onlinedocs/gcc/Atomic-Builtins.html Thus, we can reduce our maintenance burden. 
For historic resons, we carry old atomic operations support in
liblitmus. This is no longer useful:
1) There is actually no client for these calls in liblitmus.
2) There is now a standard gcc API for this purpose.

	http://gcc.gnu.org/onlinedocs/gcc/Atomic-Builtins.html

Thus, we can reduce our maintenance burden.
refactor: remove all architecture-dependent code from include/ 2010-11-09T21:35:33+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-11-06T20:46:55+00:00 1e82ca830c3ad2fd057b4c4fc5243b0622526473 Move the architecture-dependent code to the arch/ subtree. 
Move the architecture-dependent code to the arch/ subtree.
avoid including header files directly 2010-11-09T21:35:32+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-11-06T20:20:13+00:00 42e747e4fe5648967c1ead5ae327b5fbbe66f2e5 The kernel warns against including header files directly. For good reason: our previous approach (just -I$KERNEL/include) caused all kinds of files to be included that should have come from /usr/include instead. This patch rewrites the Makfile so that the (few) needed headers are copied into the liblitmus src tree before compiling the library. This avoids having to specify the kernel include directories with -I, and also makes it easier to link against liblitmus (external applications do not need to know where the kernel is). Finally, this allows us to enable -Werror. 
The kernel warns against including header files directly. For good
reason: our previous approach (just -I$KERNEL/include) caused all
kinds of files to be included that should have come from /usr/include
instead.

This patch rewrites the Makfile so that the (few) needed headers are
copied into the liblitmus src tree before compiling the library. This
avoids having to specify the kernel include directories with -I, and
also makes it easier to link against liblitmus (external applications
do not need to know where the kernel is).

Finally, this allows us to enable -Werror.
zero out rt_task parameters before setting them 2010-09-22T16:46:02+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-09-22T16:46:02+00:00 be6bf3ca538405037fb04ee2584ea57435c9770b This avoids passing random stack contents to the kernel if the structure gained some fields due to plugin development. (Also, fix up some white space issues while we are at it.) 
This avoids passing random stack contents to the kernel
if the structure gained some fields due to plugin development.

(Also, fix up some white space issues while we are at it.)
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 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