Changes between Version 21 and Version 22 of GSoC/2015/NestedMutex


Ignore:
Timestamp:
Jan 3, 2016, 6:26:22 PM (4 years ago)
Author:
Ralph Holmes
Comment:

Fix spelling and/or grammar.

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2015/NestedMutex

    v21 v22  
    7575
    7676
    77 There are two places in our JPF implementation where we have used locks over executing thread to avoid data races for SMP targets which RTEMS does not uses. So we have analysed the test case results after removing the lock  over executing thread. With the help of failing test cases we want to reproduce the same data race problem as detected by JPF in RTEMS and resolve the issue for SMP as well. These branches are created rtemsjpf-0.6-b2 and then we have removed the lock over executing thread.
     77There are two places in our JPF implementation where we have used locks over executing thread to avoid data races for SMP targets which RTEMS does not uses. So we have analyzed the test case results after removing the lock  over executing thread. With the help of failing test cases we want to reproduce the same data race problem as detected by JPF in RTEMS and resolve the issue for SMP as well. These branches are created rtemsjpf-0.6-b2 and then we have removed the lock over executing thread.
    7878
    79794. without_exec_lock [https://github.com/saurabhgadia4/lock-model/tree/without_exec_lock link] - removing lock over executing thread in lock() when mutex is not available. Because of this we get data race issues in this branch which are detected by the subset of good test cases.