| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Can events be applied to LITMUS code instead of sched_task_trace ?
PROS:
- architectural indipendency
- easy porting on newer kernel version
- lock free ring buffer implementation already there
CONS:
- need userspace tools conversion to slightly different format
- is it possible to replicate all the previous functionalities?
- only sched_trace_* functions can be implemented through events,
TRACE() debugging features are still implemented in the old way
(??? cannot we simply use the tracing features of the kernel for
debugging purposes ????)
|
| | |
|
| |
|
|
| |
- insert arm_release_timer() in add_relese() path
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
to be merged:
- arm_release_timer() with no rq locking
|
| | |
|
| |
|
|
|
|
|
|
| |
- fix requesting more than 2^11 pages (MAX_ORDER)
to system allocator
to be merged:
- feather-trace generic implementation
|
| | |
|
|
|
to be merged:
- SRP (sched.c)
- feather-trace implementation (to be fixed)
- sync support (KConfig)
litmus_sched_class implements 3 new methods:
.prio_changed:
void
.switched_to:
void
.get_rr_interval:
return infinity (i.e., 0)
|
