[LITMUS^RT] help with implementing energy-aware features in litmus-rt

[Gabriel Lozano]

hi there, i'm new to litmus-rt and i was hoping that someone here might be
able to help me with implementing energy-aware features in litmus-rt

some background: i've completed the tutorials in the litmus-rt website, and
have read (i think) every published material that explains the inner
workings of litmus-rt. i have a basic understanding of the plugin's source
code and can manage with linux development.

now, what i want is to implement scheduler plugins that featured the
following:
 (i) frequency scaling (thru the cpufreq subsystem), and
 (ii) entering/exiting sleep states (thru the cpuidle subsystem)

basically what i want is a scheduler that scaled the whole platform's (i.e.
all cores') frequency to a precomputed frequency at an offline stage.
further, during run-time, i'd like the scheduler to reclaim dynamic slacks
(i.e. diff. between WCET and AET) in the schedule, using this spare
capacity to select and enter an appropriate sleep state (maybe programming
a timer that waked up the core at the end of the sleep period). i'm not
interested in cpu-hotplug.

i am aware that currently litmus-rt does not feature/support this
functionality, although i'm not sure why (where does this conflict with
litmus's mechanisms?). i haven't found any information in the archives
regarding energy-saving features (other than asking if it's feasible). the
"getting started with litmus-rt" slides only mention this very briefly
(regarding frequency scaling it says: –plugins "work", but oblivious to
speed changes–).

i'd need to implement these features for a project, but am not sure where
to start. it'd be wonderful if someone could help me with a high-level list
of things to do to accomplish this (which litmus-rt subsystems to modify,
where to be careful with what, i don't mean to take anyone's time, i just
want to be pointed in the right direction), given that people in this list
include the core maintainers (and creators) of litmus-rt.

i'd really appreciate it if you helped me with this, 'cause i'm kind of
running out of ideas here :-). thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20170523/1466824f/attachment.html>