benchutil: Clarify unset_alarm()'s semantics
authorBarret Rhoden <brho@cs.berkeley.edu>
Thu, 6 Apr 2017 19:01:00 +0000 (15:01 -0400)
committerBarret Rhoden <brho@cs.berkeley.edu>
Wed, 3 May 2017 16:13:02 +0000 (12:13 -0400)
commit7e6d638bb795da78d8bf6079cb0ba54a63ffa082
tree284ae8dbdc5b3ba6912cb6e52f38abee6fce0488
parented0420d4d18ac6c3cae5dce6ba60817ada6b51c2
benchutil: Clarify unset_alarm()'s semantics

Userspace alarm code is based off older versions of the kernel's alarms.
But they both have the same semantics for unset: when unset returns, the
alarm handler has either completed or will never fire.

If we want to support the "non-IRQ" style alarm handlers, we'll probably
want to report the guts of the kernel's tchain code (maybe with CVs).

Signed-off-by: Barret Rhoden <brho@cs.berkeley.edu>
user/benchutil/alarm.c