| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The logic for cancelling a remote timer allowed timers to be
enqueued twice in the pull list. A method hrtimer_pull_cancel() was
added to hrtimer.c to cancel the timers properly.
Finish-switch was added to fix a stack bug. This required a change
to the global_preempt check in update_crit_levels
|
| | |
|
| | |
|
| |
|
|
|
| |
This required fixes to hrtimer_start_on code so that events can be cancelled
or re-armed while an hrtimer pull is in progress.
|
| |
|
|
|
|
|
|
|
|
|
| |
Timers had an issue where they couldn't be cancelled before they migrated.
Now when you set the start_on_info to inactive, it will prevent a timer
from being armed.
When a task is being blocked and preempted concurrently, the blocking code
needs to be able to prevent the task from being scheduled on another CPU.
This did not work for CE domains. Added a per-domain remove function
which, for ce domains, will prevent a task from being returned by the domain.
|
| | |
|
| |
|
|
|
|
|
| |
Some things are working, but the kernel panics when you try and
deallocate an event group.
Committed so Jonathan can look at it.
|
| |\
| |
| |
| | |
ssh://cvs.cs.unc.edu/cvs/proj/litmus/repo/litmus2010 into wip-mc
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
THIS CODE IS UNTESTED
We now initialize one event group for each cpu on system start. We can
get the event group for a CPU via a function in event_group.c
Another change is that an event now stores what group it is in when it
add_event() is called on it. This lets us cancel it without knowing what
event group it is in.
The above is important because Level-C events (like releases) have a
NULL event group. When calling add_event(), it will get the event group
of the current CPU. If the event needs to be canceled later, we need
that saved group in the event so we know where to remove it from.
|
| |/ |
|
| |\ |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
