getitimer(2), setitimer(2): unlock syscalls

With the changes in kern_time.c v1.150, neither getitimer(2) nor
setitimer(2) need the kernel lock anymore.

ok anton@, mpi@

diff --git a/sys/kern/syscalls.master b/sys/kern/syscalls.master
index 3375825..e377376 100644 (file)
--- a/sys/kern/syscalls.master
+++ b/sys/kern/syscalls.master
@@ -1,4 +1,4 @@
-;      $OpenBSD: syscalls.master,v 1.209 2021/03/18 08:43:38 mvs Exp $
+;      $OpenBSD: syscalls.master,v 1.210 2021/05/04 18:10:24 cheloha Exp $
 ;      $NetBSD: syscalls.master,v 1.32 1996/04/23 10:24:21 mycroft Exp $
 
 ;      @(#)syscalls.master     8.2 (Berkeley) 1/13/94
@@ -159,10 +159,10 @@
                            struct timezone *tzp); }
 68     STD NOLOCK      { int sys_settimeofday(const struct timeval *tv, \
                            const struct timezone *tzp); }
-69     STD             { int sys_setitimer(int which, \
+69     STD NOLOCK      { int sys_setitimer(int which, \
                            const struct itimerval *itv, \
                            struct itimerval *oitv); }
-70     STD             { int sys_getitimer(int which, \
+70     STD NOLOCK      { int sys_getitimer(int which, \
                            struct itimerval *itv); }
 71     STD             { int sys_select(int nd, fd_set *in, fd_set *ou, \
                            fd_set *ex, struct timeval *tv); }