litmus-rt.git/include, branch 2010.2 The LITMUS^RT kernel. Litmus core: add plugin-independent precise budget enforcement infrastructure 2010-10-19T13:40:41+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-10-18T20:01:10+00:00 576b1ad144f81d3fd3bd37d18dab86cd1e8660b0 Simple logic: if a task requires precise enforcement, then program a hr-timer to fire when the task must be descheduled. When the timer fires, simply activate the scheduler. When we switch to a different task, either reprogram the timer or cancel it. 
Simple logic: if a task requires precise enforcement, then program a
hr-timer to fire when the task must be descheduled. When the timer
fires, simply activate the scheduler. When we switch to a different
task, either reprogram the timer or cancel it.
Litmus core: add macro to test for PRECISE_ENFORCEMENT 2010-10-19T13:40:40+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-09-22T21:56:59+00:00 9b718afbc5db5a808804a336c17ba896a9f048a1 Required for EDF-WM. We should implement precise enforcement in the core distribution soon anyway (once we know how it works in EDF-WM). 
Required for EDF-WM. We should implement precise enforcement
in the core distribution soon anyway (once we know how it
works in EDF-WM).
Litmus core: add budget_remaining() helper 2010-10-19T13:40:39+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-10-18T19:58:27+00:00 bf34c69c682443b5bf2f9009b1a0039fd60e654f Quick way to figure out how much budget a LITMUS^RT job has left. 
Quick way to figure out how much budget a LITMUS^RT job has left.
hrtimer: add init function to properly set hrtimer_start_on_info params 2010-10-19T13:40:38+00:00 Andrea Bastoni bastoni@cs.unc.edu 2010-09-28T15:08:17+00:00 bd6d5f1dd586a27c2082ad4d95ee58913b471f5c This helper function is also useful to remind us that if we use hrtimer_pull outside the scope of triggering remote releases, we need to take care of properly set the "state" field of hrtimer_start_on_info structure. 
This helper function is also useful to remind us that if we use
hrtimer_pull outside the scope of triggering remote releases, we need to
take care of properly set the "state" field of hrtimer_start_on_info
structure.
rt_domain_t: add add_release_on() 2010-10-18T21:07:27+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-09-22T02:49:37+00:00 8cc60b37588e130bed9d418bcfbe4d64c3a91935 This API addition allows the calling code to override the release master for a given rt_domain_t object. This is particularly useful if a job is supposed to migrate to a particular CPU. This need arises for example in semi- partitioned schedulers. 
This API addition allows the calling code to override
the release master for a given rt_domain_t object. This
is particularly useful if a job is supposed to migrate
to a particular CPU. This need arises for example in semi-
partitioned schedulers.
Make platform-specific Feather-Trace depend on !CONFIG_DEBUG_RODATA 2010-06-01T14:43:11+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-05-31T16:52:35+00:00 753fb14dfb0662e1d38758ffc6876c0ab1c7bd9e Feather-Trace rewrites instructions in the kernel's .text segment. This segment may be write-protected if CONFIG_DEBUG_RODATA is selected. In this case, fall back to the default flag-based Feather-Trace implementation. In the future, we could either adopt the ftrace method of rewriting .text addresses using non-.text mappings or we could consider replacing Feather-Trace with ftrace altogether. For now, this patch avoids unexpected runtime errors. 
Feather-Trace rewrites instructions in the kernel's .text segment.
This segment may be write-protected if CONFIG_DEBUG_RODATA is selected.
In this case, fall back to the default flag-based Feather-Trace
implementation. In the future, we could either adopt the ftrace method
of rewriting .text addresses using non-.text mappings or we could
consider replacing Feather-Trace with ftrace altogether.

For now, this patch avoids unexpected runtime errors.
Make smp_send_pull_timers() optional. 2010-06-01T14:23:14+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-05-30T23:50:52+00:00 8bf9de45b663e4b9ce889eb24929ce773f306339 There is currently no need to implement this in ARM. So let's make it optional instead. 
There is currently no need to implement this in ARM.
So let's make it optional instead.
Make release master support optional 2010-06-01T14:23:13+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-05-30T23:46:21+00:00 cedc8df1cf1ff935af5455a9d565dac05192a47f Introduces CONFIG_RELEASE_MASTER and makes release master support dependent on the new symbol. This is useful because dedicated interrupt handling only applies to "large" multicore platforms. This will allow us to not implement smp_send_pull_timers() for all platforms. 
Introduces CONFIG_RELEASE_MASTER and makes release
master support dependent on the new symbol. This is
useful because dedicated interrupt handling only applies
to "large" multicore platforms. This will allow us to
not implement smp_send_pull_timers() for all platforms.
Make __ARCH_HAS_FEATHER_TRACE a proper CONFIG_ variable. 2010-05-31T00:43:19+00:00 Bjoern B. Brandenburg bbb@cs.unc.edu 2010-05-30T22:41:28+00:00 152968b15afb74a6adba6d512c5eebf0280c8f00 The idea of the Feather-Trace default implementation is that LITMUS^RT should work without a specialized Feather-Trace implementation present. This was actually broken. Changes litmus/feather_trace.h to only include asm/feather_trace.h if actually promised by the architecture. 
The idea of the Feather-Trace default implementation is that LITMUS^RT should
work without a specialized Feather-Trace implementation present. This was
actually broken.

Changes litmus/feather_trace.h to only include asm/feather_trace.h if actually
promised by the architecture.
Added support for choices in budget policy enforcement. 2010-05-30T15:27:34+00:00 Glenn Elliott gelliott@koruna.cs.unc.edu 2010-05-20T18:33:27+00:00 6f89d4f31485546674187cf3b4d472f230b263d0 NO_ENFORCEMENT - A job may execute beyond its declared execution time. Jobs notify the kernel that they are complete via liblitmus's sleep_next_period() QUANTUM_ENFORCEMENT - The kernel terminates a job if its actual execution time exceeds the declared execution time. PRECISE_ENFORCEMENT - Hook declared, but not yet implemented. Plan to support this policy through hrtimers. Error thrown if specified. 
NO_ENFORCEMENT - A job may execute beyond its declared execution time.
  Jobs notify the kernel that they are complete via liblitmus's
  sleep_next_period()
QUANTUM_ENFORCEMENT - The kernel terminates a job if its actual execution
  time exceeds the declared execution time.
PRECISE_ENFORCEMENT - Hook declared, but not yet implemented.  Plan to
  support this policy through hrtimers.  Error thrown if specified.