Investigate on volatiles, that do not allow optimizations. They should not be required, but without them bw2Q(), which uses l_mul_shr, outputs zero instead of the correct value.
Investigate on volatiles, that do not allow optimizations. They should not be required, but without them bw2Q(), which uses l_mul_shr, outputs zero instead of the correct value.
Investigate on volatiles, that do not allow optimizations. They should not be required, but without them bw2Q(), which uses l_mul_shr, outputs zero instead of the correct value.
Investigate on volatiles, that do not allow optimizations. They should not be required, but without them bw2Q(), which uses l_mul_shr, outputs zero instead of the correct value.
Investigate on volatiles, that do not allow optimizations. They should not be required, but without them bw2Q(), which uses l_mul_shr, outputs zero instead of the correct value.
Investigate on volatiles, that do not allow optimizations. They should not be required, but without them bw2Q(), which uses l_mul_shr, outputs zero instead of the correct value.
Check what are the proper flags to use with kmalloc().
These functions may be made static inline.
Check status of library/QRESMod inside each function
qres library level calls take pid_t; qres supervisor-filtered calls take struct task_struct (they use task info in order to enforce qossup policy); qres lowest level calls (cbs) take struct cbs_struct;
Supervisor (Tom) Invariant-based Ctrl and Pred (Tom) Translation of qosres to IRIS (Luca) Port to 2.4.27 Test inside 2.4.27 Overhead measurements
Add synchronization primitives.
After a while the QSUP goes on, the truncations in computations might lead to very bad things. A fix could be a periodic/sporadic recomputation of all values, including partials and totals.
All globals should be placed inside a structure, to be instantiated one time for each RR-enabled processor, for SMP systems.
use one for each CPU ?
evaluate if using read_lock_irqsave() is worth for anything
Check flow diagram of task add/remove/block/unblock/stop/continue w.r.t. call to rres_schedule() and/or to sync_with_server() and related
fare versioni con attach/detach_all (pensarle gia' con un interfaccia comoda da usare con dei set di task?)
Remove the rres_sync_after_add() stuff, which should be dealt with in rres_schedule().
Check that, while moving from default_srv, task is dispatched before removal from default_srv
Investigate on volatiles, that do not allow optimizations. They should not be required, but without them bw2Q(), which uses ul_mul_shr, outputs zero instead of the correct value.
Investigate on volatiles, that do not allow optimizations. They should not be required, but without them bw2Q(), which uses ul_mul_shr, outputs zero instead of the correct value.
Investigate on volatiles, that do not allow optimizations. They should not be required, but without them bw2Q(), which uses ul_mul_shr, outputs zero instead of the correct value.
Investigate on volatiles, that do not allow optimizations. They should not be required, but without them bw2Q(), which uses ul_mul_shr, outputs zero instead of the correct value.
Investigate on volatiles, that do not allow optimizations. They should not be required, but without them bw2Q(), which uses ul_mul_shr, outputs zero instead of the correct value.
Investigate on volatiles, that do not allow optimizations. They should not be required, but without them bw2Q(), which uses ul_mul_shr, outputs zero instead of the correct value.