From: Anna-Maria Gleixner Date: Thu, 21 Dec 2017 10:41:50 +0000 (+0100) Subject: hrtimer: Make remote enqueue decision less restrictive X-Git-Tag: v4.16-rc1~176^2~11 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2ac2dccce9d16a7b1a8fddf69a955d249375bce4;p=thirdparty%2Fkernel%2Flinux.git hrtimer: Make remote enqueue decision less restrictive The current decision whether a timer can be queued on a remote CPU checks for timer->expiry <= remote_cpu_base.expires_next. This is too restrictive because a timer with the same expiry time as an existing timer will be enqueued on right-hand size of the existing timer inside the rbtree, i.e. behind the first expiring timer. So its safe to allow enqueuing timers with the same expiry time as the first expiring timer on a remote CPU base. Signed-off-by: Anna-Maria Gleixner Cc: Christoph Hellwig Cc: John Stultz Cc: Linus Torvalds Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: keescook@chromium.org Link: http://lkml.kernel.org/r/20171221104205.7269-22-anna-maria@linutronix.de Signed-off-by: Ingo Molnar --- diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c index 1c68bf21f603c..f4a56fbae662d 100644 --- a/kernel/time/hrtimer.c +++ b/kernel/time/hrtimer.c @@ -168,7 +168,7 @@ hrtimer_check_target(struct hrtimer *timer, struct hrtimer_clock_base *new_base) ktime_t expires; expires = ktime_sub(hrtimer_get_expires(timer), new_base->offset); - return expires <= new_base->cpu_base->expires_next; + return expires < new_base->cpu_base->expires_next; } static inline