Set tchain earliest/latest on any removal
authorBarret Rhoden <brho@cs.berkeley.edu>
Fri, 15 Jun 2018 21:27:05 +0000 (17:27 -0400)
committerBarret Rhoden <brho@cs.berkeley.edu>
Fri, 15 Jun 2018 21:27:05 +0000 (17:27 -0400)
commit4344ce2755c16525f241be6155c62fceddfec00b
tree9c9638812d02214a8eba2774be3bb888febca059
parent6197d577a6098582588d95bd3704e0d5143b86b7
Set tchain earliest/latest on any removal

Alarm handlers can put themselves back on the tchain during their handler.
The logic for that involves the earliest/latest times.  Those times should
change since the old awaiter (which is running) was yanked off.

I didn't have any actual problems with this, but it popped up as a
potential issue.

Signed-off-by: Barret Rhoden <brho@cs.berkeley.edu>
kern/src/alarm.c
tests/alarm.c
user/parlib/alarm.c