| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
move the switch_from/switch_to trace macros so that the
scheduling overhead shows up more clearly in the traces
|
|
|
|
|
| |
A release master is a CPU that takes all timer interrupts for
release of a given rt_domain_t. By default off.
|
|
|
|
| |
this was never strictly required, so we might as well avoid it
|
| |
|
|
|
|
| |
this removes a blatant case of copy&paste reuse
|
|
|
|
|
| |
This establishes the architectures dependent bits for hrtimer_start_on()
on x86-32.
|
|
|
|
|
| |
This depends on the ability to send the special 'pull_timers' IPI
even with IRQs disabled.
|
| |
|
|
|
|
| |
Helps when debugging wake-up related crashes.
|
|
|
|
|
|
| |
Lockdep doesn't like the heap's locking pattern. We'd have
to allocate a locking class for each cheap_node, which is a bit
excessive memory-wise.
|
|
|
|
| |
Variable declarations go first.
|
| |
|
|\ |
|
| |\ |
|
| | |
| | |
| | |
| | | |
No plugin uses it anymore.
|
| | | |
|
| | |
| | |
| | |
| | | |
a good base version for other schedulers
|
| | |
| | |
| | |
| | |
| | |
| | | |
Doing it task-by-task really only makes sense if
we are going to trace every merged task in the debug
trace.
|
| | |
| | |
| | |
| | |
| | | |
Tell Linux how much time each RT task consumed.
This fixes the behavior of CPU timers and tools like top.
|
| | |
| | |
| | |
| | | |
It won't compile with missing prototypes.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Don't multiplex one timer among all release heaps.
The hrtimer subsystem can handle many timers and is
heavily optimize; make use of this fact.
This also greatly simplifies the actual callback, which
should help to bring down release overheads.
This also saves memory as we do not need to maintain a separate
heap of (release) heaps.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes a bunch of bugs:
- a memory leak (some heap nodes were never reclaimed)
- a locking rules violation (memory allocation can wake up kswapd,
which causes a circular locking dependency between the release queue lock
and the run queue locks
Also, allocating memory in a hot path was never particularly clever.
This patch pre-allocates memory at task-creation time, but does not change
how the release queue works overall.
|
| | |
| | |
| | |
| | | |
Prepare for centralized allocation of release heaps.
|
| | |
| | |
| | |
| | | |
Avoid duplication.
|
| | |
| | |
| | |
| | |
| | | |
Comparing a task against itself shouldn't
happen if everything works correctly.
|
| | |
| | |
| | |
| | | |
Support for Global Quantum-Driven EDF
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the infrequent case that arm_release_timer() is called
while the timer callback is executing on the same CPU
(e.g., a timer tick occurred), then hrtimer_cancel() will
get stuck in an infinite loop. This can be avoided by using
hrtimer_try_to_cancel() instead.
|
| | |
| | |
| | |
| | |
| | | |
Don't confuse the plugins by calling task_block()/wake_up()
when they wouldn't have been called without the race.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Other quantum-based plugins also require the present flag. Hence,
move it to the core data structure
|
| |/
|/| |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
A simple noop system call to record kernel entry and exit
times.
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
struct x* p = kmalloc(sizeof(struct x), ....)
becomes
struct x* p = kmalloc(sizeof(*p), ...)
for example.
|
|/ |
|
| |
|
|
|
|
|
|
| |
- better tracing
- cleaner release code
- add FIXME
|
|
|
|
|
| |
- fix end of tick preempt logic
- make scheduler resilient against missed quanta
|
| |
|
|
|
|
| |
Quiets a warning.
|
|
|
|
|
| |
1000 was limiting since the sync. release code
wants a 1 second delay per default.
|
|
|
|
| |
Much of the tracing is not needed anymore.
|
| |
|
|
|
|
| |
Used to correct for staggering in time->quanta computations
|
|
|
|
| |
The list traversal code was horribly broken.
|
| |
|
|
|
|
|
| |
The previous version did not get the release
time right in most cases.
|
|
|
|
|
| |
-1 doesn't make sense for an unsigned field and screws up
the log viewer.
|
|
|
|
| |
Give plugins a chance to set up state and clean up.
|
|
|
|
| |
Let scheduler plugins inquire stagger offsets.
|