From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751695AbdHaMXn (ORCPT ); Thu, 31 Aug 2017 08:23:43 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:60556 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751625AbdHaMXk (ORCPT ); Thu, 31 Aug 2017 08:23:40 -0400 Message-Id: <20170831105826.438898127@linutronix.de> User-Agent: quilt/0.63-1 Date: Thu, 31 Aug 2017 12:23:38 -0000 From: Anna-Maria Gleixner To: LKML Cc: Peter Zijlstra , Ingo Molnar , Christoph Hellwig , keescook@chromium.org, John Stultz , Thomas Gleixner Subject: [PATCH 11/25] hrtimer: Allow remote hrtimer enqueue with "expires_next" as expiry time References: <20170831105725.809317030@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline; filename=hrtimer--check-target-fix.patch Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When enqueuing a timer with expiry X into a timer queue, where already a timer with expriy X is queued, the new timer is queued on the right-hand side of the already queued timer. Therefore it is no problem, to enqueue a hrtimer on a remote CPU with the same expiry time than the programmed expiry time (expires_next) on this CPU, because the reprogramming path is not executed - it is not the "leftmost" hrtimer. Signed-off-by: Anna-Maria Gleixner --- kernel/time/hrtimer.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/kernel/time/hrtimer.c +++ b/kernel/time/hrtimer.c @@ -168,7 +168,7 @@ hrtimer_check_target(struct hrtimer *tim 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; } #ifdef CONFIG_NO_HZ_COMMON