[RTEMS Project] #2631: Use an ISR lock to protect the state of Classic Rate Monotonic objects

RTEMS trac trac at rtems.org
Tue Mar 22 06:28:14 UTC 2016


#2631: Use an ISR lock to protect the state of Classic Rate Monotonic objects
-----------------------------+------------------------------
 Reporter:  sebastian.huber  |       Owner:  sebastian.huber
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:  4.12
Component:  cpukit           |     Version:  4.10
 Severity:  normal           |  Resolution:  fixed
 Keywords:                   |
-----------------------------+------------------------------
Changes (by Sebastian Huber <sebastian.huber@…>):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"90960bd11a91259d9aace3870692dbe2e227de0f/rtems"]:
 {{{
 #!CommitTicketReference repository="rtems"
 revision="90960bd11a91259d9aace3870692dbe2e227de0f"
 rtems: Rework rate-monotonic scheduler

 Use the default thread lock to protect rate-monotonic state changes.
 This avoids use of the Giant lock.  Split rtems_rate_monotonic_period()
 body into several static functions.  Introduce a new thread wait class
 THREAD_WAIT_CLASS_PERIOD for period objects to synchronize the blocking
 operation.

 Close #2631.
 }}}

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


More information about the bugs mailing list