timekeeping: Encapsulate locking/unlocking of timekeeper_lock
authorThomas Gleixner <tglx@linutronix.de>
Wed, 9 Oct 2024 08:29:01 +0000 (10:29 +0200)
committerThomas Gleixner <tglx@linutronix.de>
Fri, 25 Oct 2024 17:49:13 +0000 (19:49 +0200)
commitdbdcf8c4caeca8192daa43429ccf23a1feec126c
treefa12b450e492f5ab61e326961c041c634fa22f06
parent20c7b582e88b8a72832637cd1754e5622aa8a92d
timekeeping: Encapsulate locking/unlocking of timekeeper_lock

timekeeper_lock protects updates of timekeeper (tk_core). It is also used
by vdso_update_begin/end() and not only internally by the timekeeper code.

As long as there is only a single timekeeper, this works fine.  But when
the timekeeper infrastructure will be reused for per ptp clock timekeepers,
timekeeper_lock needs to be part of tk_core..

Therefore encapuslate locking/unlocking of timekeeper_lock and make the
lock static.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Anna-Maria Behnsen <anna-maria@linutronix.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: John Stultz <jstultz@google.com>
Link: https://lore.kernel.org/all/20241009-devel-anna-maria-b4-timers-ptp-timekeeping-v2-8-554456a44a15@linutronix.de
kernel/time/timekeeping.c
kernel/time/timekeeping_internal.h
kernel/time/vsyscall.c