[RTEMS Project] #2556: Implement the O(m) Independence-Preserving Protocol (OMIP)

RTEMS trac trac at rtems.org
Fri May 20 14:13:25 UTC 2016


#2556: Implement the O(m) Independence-Preserving Protocol (OMIP)
-----------------------------+------------------------------
 Reporter:  sebastian.huber  |       Owner:  sebastian.huber
     Type:  enhancement      |      Status:  accepted
 Priority:  normal           |   Milestone:  4.12
Component:  cpukit           |     Version:  4.12
 Severity:  normal           |  Resolution:
 Keywords:                   |
-----------------------------+------------------------------

Comment (by Sebastian Huber <sebastian.huber@…>):

 In [changeset:"7dfb4b970cbd22cef170b2f45a41f445406a2ce5/rtems"]:
 {{{
 #!CommitTicketReference repository="rtems"
 revision="7dfb4b970cbd22cef170b2f45a41f445406a2ce5"
 score: Add per scheduler instance maximum priority

 The priority values are only valid within a scheduler instance.  Thus,
 the maximum priority value must be defined per scheduler instance.  The
 first scheduler instance defines PRIORITY_MAXIMUM.  This implies that
 RTEMS_MAXIMUM_PRIORITY and POSIX_SCHEDULER_MAXIMUM_PRIORITY are only
 valid for threads of the first scheduler instance.  Further
 API/implementation changes are necessary to fix this.

 Update #2556.
 }}}

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


More information about the bugs mailing list