Changes between Version 1 and Version 2 of GSoC/2015/NestedMutex


Ignore:
Timestamp:
Jun 5, 2015, 6:18:57 AM (5 years ago)
Author:
Saurabh Gadia
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2015/NestedMutex

    v1 v2  
    55'''Participant:''' Saurabh Gadia
    66
    7 '''Status''' Currently working on configuring and designing the nested mutex validation model in JPF environment for proposed solution.
     7'''Status:''' Currently working on configuring and designing the nested mutex validation model in JPF environment for proposed solution.
    88
    9 '''Introduction''' The strict order mutexes in RTEMS is based on LIFO ordering. So whenever thread tries to acquire mutex lock, its priority before acquiring the lock is pushed to that mutex’s thread queue. So whenever thread release any lock then that lock’s queue is consulted and thread’s priority is restored. So this mechanism of restoring priority may induce unbounded priority inversion if higher priority thread is contending for a lock still hold by our candidate thread. This project deals with solving this problem and developing validation methods using JPF.
     9'''Introduction:''' The strict order mutexes in RTEMS is based on LIFO ordering. So whenever thread tries to acquire mutex lock, its priority before acquiring the lock is pushed to that mutex’s thread queue. So whenever thread release any lock then that lock’s queue is consulted and thread’s priority is restored. So this mechanism of restoring priority may induce unbounded priority inversion if higher priority thread is contending for a lock still hold by our candidate thread. This project deals with solving this problem and developing validation methods using JPF.
    1010
    1111= Progress =