| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
| |
Also changed the LITMUS_TRY/LITMUS_CATCH/END_LITMUS_TRY macros
to use if/else-if chains instead of switch statements. This is
because SIGRTMAX is a variable in libc and not a compile-time
constant (switches cant be used).
|
| |
|
|
|
| |
The timing functions are quite handy when building benchmark tasks.
Avoid copy&paste reuse by making them available via the library.
|
| |
|
|
|
| |
We want the positive loop length, not the negative, to prevent jobs
from overruning their budget.
|
| |
|
|
|
| |
Using cputime() is much more accurate than the old delay loop
auto-configuration. There is no good reason to keep it around.
|
| |
|
|
|
| |
Still need to figure out what to do with the period is less than the
exec_cost (or budget).
|
| |
|
|
|
| |
rtspin produces prettier schedules if it transitions to non-real-time
mode before terminating.
|
| |
|
|
|
|
| |
This should only trigger if the execution time tracking is broken (as
it was on District10). With the emergency exit, we at least prevent
the system from becoming unresponsive.
|
| |
|
|
| |
Useful to test how the kernel handles PRECISE_ENFORCEMENT.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Can be used to dump the delay loop that rtspin
is using.
|
| | |
|
| | |
|
| |
|
|
| |
this finally appears to work reasonably on Flare
|
| |
|
|
|
| |
Don't just blindly overrun the budget.
Instead, try to measure a spin loop and hope that we get good results.
|
| |
|
