Changes between Version 4 and Version 5 of GSoC/2015/NestedMutex


Ignore:
Timestamp:
Jun 5, 2015, 11:42:49 PM (6 years ago)
Author:
Saurabh Gadia
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2015/NestedMutex

    v4 v5  
    99'''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
     11= Configuration Setup Steps =
     12  * Build RSB by following this [https://docs.rtems.org/rsb link] from 1.0 to 2.4 Building step(inclusive).
     13  * Now clone the RTEMS repository from [https://github.com/saurabhgadia4/rtems Personal Github Link]
     14
     15{{{
     16sudo apt-get install pax    (you require it for compiling libtests from testsuite) This step should be performed before bootstraping.
     17
     18cd rtems
     19
     20export PATH=/opt/rtems/4.11/bin:$PATH
     21
     22export PATH=~/devlopment/rtems/4.11/bin:$PATH
     23
     24./bootstrap
     25
     26cd ..
     27
     28mkdir b-sis
     29
     30cd b-sis
     31
     32../rtems/configure --target=sparc-rtems4.11 --enable-rtemsbsp=sis --enable-tests --disable-posix ENABLE_STRICT_ORDER_MUTEX=1
     33
     34make
     35
     36sudo PATH=/opt/rtems/4.11/bin:${PATH} make install
     37}}}
     38
     39  * Above steps if performed correctly will compile your RTEMS code and you can go ahead with your test suites.
    1140= Progress =
    1241  * Proposed solution for the existing problem. You can find presentation which also contains test cases in attachment section.