#2173: Potential integer overflow problem in EDF scheduler -----------------------------+---------------------------- Reporter: sebastian.huber | Owner: joel.sherrill Type: defect | Status: reopened Priority: normal | Milestone: 4.11 Component: cpukit | Version: 4.11 Severity: normal | Resolution: Keywords: | -----------------------------+----------------------------
Comment (by joel.sherrill): The EDF scheduler should NOT use priority to store the deadline. That is one issue and it shows itself by bogus values being returned when you obtain the current priority. So #2 is **NOT** acceptable to me. The EDF scheduler should use its own internal stored value to sort the threads. Why can't the scheduler use uptime and not ticks since boot? The EDF scheduler is broken in assuming it can rewrite a thread priority with a deadline. -- Ticket URL: <http://devel.rtems.org/ticket/2173#comment:5> RTEMS Project <http://www.rtems.org/> RTEMS Project _______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs