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

Timestamp:

06/05/15 23:42:49 (9 years ago)

Author:

Saurabh Gadia

Comment:

--

GSoC/2015/NestedMutex

@@ -9 +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. 
 
+= Configuration Setup Steps =
+  * Build RSB by following this [https://docs.rtems.org/rsb link] from 1.0 to 2.4 Building step(inclusive).
+  * Now clone the RTEMS repository from [https://github.com/saurabhgadia4/rtems Personal Github Link] 
+
+{{{
+sudo apt-get install pax    (you require it for compiling libtests from testsuite) This step should be performed before bootstraping.
+
+cd rtems
+
+export PATH=/opt/rtems/4.11/bin:$PATH
+
+export PATH=~/devlopment/rtems/4.11/bin:$PATH
+
+./bootstrap
+
+cd ..
+
+mkdir b-sis
+
+cd b-sis
+
+../rtems/configure --target=sparc-rtems4.11 --enable-rtemsbsp=sis --enable-tests --disable-posix ENABLE_STRICT_ORDER_MUTEX=1
+
+make
+
+sudo PATH=/opt/rtems/4.11/bin:${PATH} make install
+}}}
+
+  * Above steps if performed correctly will compile your RTEMS code and you can go ahead with your test suites.
 = Progress = 
   * Proposed solution for the existing problem. You can find presentation which also contains test cases in attachment section.