PI Mutex Test

From RTwiki
(Difference between revisions)
Jump to: navigation, search
(External links)
(updating docs on PI tests)
Line 18: Line 18:
 
To use, create a directory and untar the archive contents into that directory. Run make, which by default will build the two tests. If things don't compile, chances are your GLIBC does not support the Priority Inheritance attribute for pthread mutexes and you will need to upgrade.
 
To use, create a directory and untar the archive contents into that directory. Run make, which by default will build the two tests. If things don't compile, chances are your GLIBC does not support the Priority Inheritance attribute for pthread mutexes and you will need to upgrade.
  
Both programs have usage messages (--help) that explain their options. The classic_pi program is generally just used to show that PI mutexes work, while the pi_stress program is used to exercies the PI code path.  
+
Both programs have usage messages (--help) that explain their options. The classic_pi program is generally just used to show that PI mutexes work, while the pi_stress program is used to exercies the PI C library/kernel code path.  
  
 
For example:
 
For example:

Revision as of 21:30, 23 October 2006

This regression test suite was written by User:Clark to test the classic three-way Priority Inversion deadlock and shows that Priority Inheritance mutexes will avoid this deadlock.

TODO
Add documentation about using the test suite

External links

This tarball contains the source code for two test programs:

  • classic_pi - a program that demonstrates how a PI mutex can resolve a Priority Inversion deadlock
  • pi_stress - a stress test that runs groups of threads that cause Priority Inversions
NOTE!
This code has only been tested on Linux 2.6.17+ with the -rt patch and GLIBC 2.5+

To use, create a directory and untar the archive contents into that directory. Run make, which by default will build the two tests. If things don't compile, chances are your GLIBC does not support the Priority Inheritance attribute for pthread mutexes and you will need to upgrade.

Both programs have usage messages (--help) that explain their options. The classic_pi program is generally just used to show that PI mutexes work, while the pi_stress program is used to exercies the PI C library/kernel code path.

For example:

# pi_stress <options>
   options:
       --quiet         - no output
       --verbose       - lots of output
       --groups=<n>    - set the number of inversion groups
       --inversions=<n>        - number of inversions per group
       --report=<path> - output to file
       --fifo          - use SCHED_FIFO for test threads
       --rr            - use SCHED_RR for test threads
       --prompt        - prompt before starting the test
       --debug         - turn on debug prints
       --version       - print version number on output
       --help          - print this message
ATTENTION!
The pi_stress program uses many realtime (SCHED_FIFO or SCHED_RR) threads and can quickly render a machine unusable (i.e. press the big red button). Do Not Use it on a production machine!
Personal tools