From c4bc0b1a64e1ef1e105df84401805a16e8dbe82a Mon Sep 17 00:00:00 2001 From: Jens Gustedt Date: Wed, 3 Jan 2018 14:17:12 +0100 Subject: consistently use the LOCK an UNLOCK macros In some places there has been a direct usage of the functions. Use the macros consistently everywhere, such that it might be easier later on to capture the fast path directly inside the macro and only have the call overhead on the slow path. --- src/thread/pthread_setschedparam.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/thread/pthread_setschedparam.c') diff --git a/src/thread/pthread_setschedparam.c b/src/thread/pthread_setschedparam.c index c4738d64..9e2fa456 100644 --- a/src/thread/pthread_setschedparam.c +++ b/src/thread/pthread_setschedparam.c @@ -3,8 +3,8 @@ int pthread_setschedparam(pthread_t t, int policy, const struct sched_param *param) { int r; - __lock(t->killlock); + LOCK(t->killlock); r = t->dead ? ESRCH : -__syscall(SYS_sched_setscheduler, t->tid, policy, param); - __unlock(t->killlock); + UNLOCK(t->killlock); return r; } -- cgit v1.2.1