diff options
| author | Josh Stone <jistone@redhat.com> | 2010-03-11 17:14:59 -0800 |
|---|---|---|
| committer | Josh Stone <jistone@redhat.com> | 2010-03-11 17:15:20 -0800 |
| commit | 0da46fcdec144f944838350f08f59a36b8709e90 (patch) | |
| tree | 8b825a01177517b50af0da37a1f422ac5a34e96e /runtime/autoconf-synchronize-sched.c | |
| parent | 40e400d07bcfa621eef5b4f4496b7af665089e55 (diff) | |
| download | systemtap-steved-0da46fcdec144f944838350f08f59a36b8709e90.tar.gz systemtap-steved-0da46fcdec144f944838350f08f59a36b8709e90.tar.xz systemtap-steved-0da46fcdec144f944838350f08f59a36b8709e90.zip | |
Fix the edge-case of MAXTRYLOCK=0
We didn't really have good semantics for what is meant by MAXTRYLOCK=0,
so when skipped.exp tried it, we ended up locking the variable and then
reporting a skip without ever unlocking it.
This is now cleaning up the semantics such that MAXTRYLOCK defines how
many times we should loop if the lock is busy. Thus MAXTRYLOCK=0 means
we try only once and fail immediately.
The testcase was accidentally creating contention due to the broken
unlock behavior. We now have to try a bit harder to create real
contention, so some lengthy delays are inserted to hoard the lock.
* runtime/probe_lock.h (stp_probe_lock): Fix the skip behavior.
* testsuite/systemtap.base/skipped.exp: Add a big udelay.
Diffstat (limited to 'runtime/autoconf-synchronize-sched.c')
0 files changed, 0 insertions, 0 deletions