| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Fix the sem_timedwait(3) test. |   cheloha | 2019-12-20 | 1 | -9/+25 |
| | | | | | | | | | | | | | | | | | | | The recent clock_getres(2) changes made it so that clock_getres(2) returns the granularity of the active timecounter. This is usually much finer than that of hardclock(9), so we can no longer use clock_getres(2) to fudge our upper timeout return bound. The test is failing because it thinks our sem_timedwait(3) call is returning with too much latency. We can still get the hardclock(9) granularity via the kern.clockrate sysctl(2), though, so just use that to fudge the upper bound. While here, we ought to be checking that we return after the requested absolute timeout, not that we were asleep for a particular interval. Breakage reported by mpi@. ok mpi@ | ||||
| * | Fix sem_timedwait regress test. Needs SA_RESTART to block now. |   pirofti | 2018-04-27 | 1 | -2/+2 |
| | | | | | Hug and OK guenther@ | ||||
| * | There can be resolution-worth of slop in two places, so accept that |   guenther | 2014-01-22 | 1 | -1/+2 |
| | | |||||
| * | Add tests for sem_timedwait() | guenther | 2012-03-03 | 3 | -2/+124 |
| | | |||||
| * | Verify that sem_wait() doesn't return zero without decrementing the | guenther | 2012-03-03 | 1 | -3/+52 |
| | | | | | | semaphore when a signal is received. It should either resume waiting or return EINTR, preferrably the former. | ||||
| * | While we guarantee that a zero-filled sem_t variable will trigger | guenther | 2012-03-03 | 3 | -6/+9 |
| | | | | | | | | EINVAL errors, a sem_t on the stack may have garbage, so make the tests portable by moving the sem_t from function to file scope. problem found by miod@ | ||||
| * | Basic semaphore tests |   mpi | 2012-01-04 | 10 | -0/+215 |
| ok guenther@ | |||||
 |
index : wireguard-openbsd | |
| WireGuard implementation for the OpenBSD kernel | Matt Dunwoodie |
| summaryrefslogtreecommitdiffstats |