| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
| |
When budgets are not enforced and is exhausted, gedf_task_replenish_budget
will not actually call prepare_for_next_period, which means it will always
be in a state of budget exhaustion, therefore never being dispatched by
the reservation.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Added support for non-preemptivity in EXT-RES.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
When multiple scheduling events occur simultaneously, a situation could
happen where:
- one core schedules a task that is linked to it
- a check_for_preemption occurs due to another scheduling event
- that task is now linked to another core
- the other core tries to schedule it but can't grab the task from the
runqueue of the other core
Solution:
Added in the scheduled_on field in gedf_reservation. This enables us in
link_task_to_cpu to check for this occuring and swap the linking so the
above situation doesn't happen. The code is taken and modified from
link_task_to_cpu in GSN-EDF
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
When using litmus's budget enforcement, due various overheads, the
task's budget and the gedf_res's budget may differ a bit. When the task
overruns its budget but due to this difference still has budget
according to gedf_res, this can cause litmus to bug out due to error
checking in litmus's budget enforcement code.
Solution:
Made sure not to dispatch the task if it's out of budget in
gedf_task_dispatch_client
|
| |
|
|
|
|
|
|
| |
Added a system call for the lock holder to check if it is
in a forbidden zone and if so, suspend until the beginning
of the next time slice for its parent component.
This does not include any "skipping ahead" mechanism.
|
| | |
|
| |
|
|
|
| |
This includes priority inheritance, but no concept of
forbidden zones.
|
| |
|
|
|
| |
This is the variant of the OMLP that uses priority inheritance,
and comes from BBB's dissertation work.
|
| |
|
|
|
| |
Reduces the size of our diff from upstream litmus and
should have no impact on functionality. Ported from MC^2.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Unlink in gedf_reservation would try to unlink a task that's not linked
nor in the ready queue. It is in fact in the release queue. This happens
when multiple check_for_preemptions occur simultaneously, and causes a
task to be "scheduled" on 2 cpu_entries simultaneously while out of
budget. Thus, both cpus in update_time replenishes the budget and tries
to unlink it. The first one succeeds, while the second fails.
For more details on how this occurs, see the comment in update_time in
gedf_reservation.c
|
| |
|
|
|
| |
Now set to ULLONG_MAX - deadline(absolute). This fixes logic issues in
using higher_res_prio when one parameter is null
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Dynamic CPU entry/exit changes:
- Fix build with CONFIG_RELEASE_MASTER
- Migrate gedf_env release timer when a core is suspended
- Fix race condition in gedf_env core resume
- Add documentation
- Allow for gedf_env_suspend() and gedf_env_resume() to be called
on CPUs that have already been suspended or resumed. (They do
nothing in those cases.)
Portability:
- Allocate space in `gedf_reservation_environment` using
`num_online_cpus()` rather than `NR_CPUS`. Otherwise the stack
frame can overflow when `NR_CPUS` is large.
- Assign `plugin_state` from the plugin rather than the extended
reservations code to support other uses of `plugin_state`.
Misc:
- Improve robustnesss of `gedf_env_is_np()`
- Don't memset with 0 memory already zeroed-out by `kzalloc()`
- Use GFP_ATOMIC for allocations when in a scheduling context
|
| |
|
|
|
|
|
|
|
|
| |
Bugs fixed:
- cpu priority comparison in gedf environment made it so cpus were
ordered opposite to what they are supposed to
- shutdown of component did not free all memory
Note: It is up to the table maker such that components do not cause
cross migrations of tasks
|
| |
|
|
|
|
|
|
|
|
| |
Fixed the following:
-reservations(both mtd and gedf) were not properly added to the all_reservations list that
allows it to be found by find_res_by_id
-mtd_reservations not linked after it has been allocated
-fixed mtd_env_dispatch logic so that when nothing is in ready_queue, it
scheduled NULL instead of currently scheduled reservation
-fixed find_res_by_id forgetting to release lock
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Also, includes WIP of component allocator. This WIP is not included in
the makefile so it won't mess up the compilation.
|
| |
|
|
|
|
|
|
|
|
|
| |
Changed gedf_reservation_environment suspend and resume logic to better support
a cleverer way of handling mapping real cpu to environment cpu_entries.
This removes the cpu_mapping variable which forces a multi-core component to
update cpu_mapping on one core(the first one to call schedule).
The new logic decentralizes this process, and allows a component to be
scheduled on a completely new set of cores in 1 scheduling pass.
|
| | |
|
| |
|
|
|
| |
Encounters problem where task waits an extra period due to
sleep(unresolved)
|
| |
|
|
| |
Works under preliminary tests
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
Didn't fail thanks to the CHECK
|
| |
|
| |
This did not turn into an error thanks to the ```CHECK(should_wait_for_stack)``` at the registering function
|
| |
|
| |
Error with the curly braquets
|
| |
|
|
|
| |
To allow userspace to determine when exactly a synchronous release
should occur.
|
| |
|
|
|
| |
The platform code does not synchronize anything, so make sure there's
only one caller at any time.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Even if a kernel is relocatable, the if-based implementation of
Feather-Trace can still work. So don't hide these options.
|
