kernel: stathz is always non-zero after cpu_initclocks()
authorcheloha <cheloha@openbsd.org>
Sat, 4 Feb 2023 19:33:03 +0000 (19:33 +0000)
committercheloha <cheloha@openbsd.org>
Sat, 4 Feb 2023 19:33:03 +0000 (19:33 +0000)
commit9bcfcad5a8f89fd60010f3485ee44bf251abde23
tree94d8b42f9b36ad7202367cecadd8d8f8b8a888bc
parent24ee467d1e5e812429867003c29e5339cd18bad7
kernel: stathz is always non-zero after cpu_initclocks()

Now that the clockintr switch is complete, cpu_initclocks() always
initializes stathz to a non-zero value.  We don't call statclock()
from hardclock(9) anymore and, more broadly, we don't need to test
whether stathz is non-zero before using it.

With input from kettenis@.

Link: https://marc.info/?l=openbsd-tech&m=167434223309668&w=2
ok kettenis@ miod@
sys/kern/kern_clock.c
sys/kern/kern_resource.c
sys/kern/kern_time.c
sys/kern/sched_bsd.c