[RTEMS Project] #2173: Potential integer overflow problem in EDF scheduler

[RTEMS trac]

#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 gedare):

 Why not rewrite thread (current) priority?

 Priority should be an opaque notion of a scheduler in general, which
 should export information needed for synchronization modules (locks) to
 implement PI/PC protocols. The priority of a thread being scheduled
 according to EDF increases (toward 0) as its deadline draws closer.

 That said, I'm not opposed to putting the absolute deadline into the
 scheduler-specific portion of the TCB. I just don't understand the strong
 negative reaction to letting the scheduler determine what priority means.

--
Ticket URL: <http://devel.rtems.org/ticket/2173#comment:6>
RTEMS Project <http://www.rtems.org/>
RTEMS Project