From patchwork Wed May 10 07:28:17 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Anna-Maria Behnsen X-Patchwork-Id: 91927 Return-Path: Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:b0ea:0:b0:3b6:4342:cba0 with SMTP id b10csp3435508vqo; Wed, 10 May 2023 00:45:09 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6q02DB0n2AmQTWQ3+x9OvBTOVHhvte9sZAeghaGTd2ixj6ATCUCbA2sX9m0Sxv016d0r5a X-Received: by 2002:a05:6a00:1915:b0:647:e45f:1a49 with SMTP id y21-20020a056a00191500b00647e45f1a49mr3027419pfi.4.1683704709657; Wed, 10 May 2023 00:45:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683704709; cv=none; d=google.com; s=arc-20160816; b=rR42gby20l3N9fS1ntqJjS6Jx+8bjDrWDVKEhFC/r4U3ygic8QAfy66K1Rwy7bDwP4 S60+W1x19pt0wp8n7FlVawDUZE0jNDKgLriG14rnWqNTnSAf2ho/SiYoKpX/5gCwKwbJ vbjclwfge1qGE1rcSOrzRchejLAyLw9r4qYOF0YWeqTh/MavKhBNDStlPxPUXElXhkB0 aSL+dTMitXxl5L9ovDFhX66lFnC/NzIf7/n8Ni4HAfLOXg2s3BZhJVevmJ+aXNCqKw5x GGn392Hb4TI6bmkrbf0c5d4K8NZDdpKWYxOLed5oVxy9FKBk74uZse1EBTAKBKSP4Vqk ba5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:dkim-signature :dkim-signature:from; bh=0BQw5u7Ek28zuVB1oZkPoCLsXOX8+9uTBHf3la7W5Lk=; b=UsGusMXUO4nxI/DNnLtrlzDQR2dpLf9WPLEsg5K1X7ZbDmGRb4MyHiFJ07wgyeb1EV ItevPrtLQJsZWlUD5RtRI9o+AoKw95vNXazx5BIBlIC+AmuEJlr4dtJma45HcJqhs2y1 Nr4LvT59bOQZhoUQwplp4H1ngA/ERgHyOiDBst5A0fhX4lM8E7MjLlypOjfEJXQsl3FV EDwY/7v4grXT8Jf4QCQt/u+R3x4tMegDoJxV9192p9qP0//JRUO4/YJZogpeaHak90cq O4oJJxz2Bac67e7dUaJt08SPthiA3vYj7pbgASC+fivNlbbYkiHodM7UGMs1ir0pWJxZ ZAPQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=KvhexZKX; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e header.b=S3fyDj00; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t17-20020a639551000000b0050c0a7a2742si3401256pgn.350.2023.05.10.00.44.56; Wed, 10 May 2023 00:45:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=KvhexZKX; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e header.b=S3fyDj00; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236427AbjEJHbT (ORCPT + 99 others); Wed, 10 May 2023 03:31:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53568 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236495AbjEJHa3 (ORCPT ); Wed, 10 May 2023 03:30:29 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A656686AD for ; Wed, 10 May 2023 00:29:46 -0700 (PDT) From: Anna-Maria Behnsen DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1683703728; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=0BQw5u7Ek28zuVB1oZkPoCLsXOX8+9uTBHf3la7W5Lk=; b=KvhexZKXipdtPtvOa72sc4ehSrzhhUNdBiOPnWcx12o/UC9D7YCVS1yTsJYlKeP7sklek5 RFw7Hs0ETCHI0r96xa9kZUbTaXzbzR2nATFKGkK50dyw/kvoTjz0Tzb2b7f6y3LufKsYVL 8bmfU3M6zyy5kamhCxIlU+WxGWvs3Y2mdi2ozGOFR3yfT8JCfVxIgfUoL/YTfiUwbQX8rp 48ItwnJ+bbk2oOQBVHxFd/zpk/r0e8VTvKq/LRGTRhb9X4jXVAt3Sy37lZfqAIGHIxdFRl UvrWwsjEv6A6kT3N7YVywtnSPY40uOhBzSwSqRvXlwcUyGnNcoBwE+2zW4uGpg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1683703728; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=0BQw5u7Ek28zuVB1oZkPoCLsXOX8+9uTBHf3la7W5Lk=; b=S3fyDj00wlxcpy4tmeSsdOx2cJjhLt4UEQJBtkl6w9+JuGBgnnMzmwFFAKtDQA8FMVjekj tr6qHpVmGLWDmRAQ== To: linux-kernel@vger.kernel.org Cc: Peter Zijlstra , John Stultz , Thomas Gleixner , Eric Dumazet , "Rafael J . Wysocki" , Arjan van de Ven , "Paul E . McKenney" , Frederic Weisbecker , Rik van Riel , Steven Rostedt , Sebastian Siewior , Giovanni Gherdovich , Lukasz Luba , "Gautham R . Shenoy" , Anna-Maria Behnsen , Richard Cochran Subject: [PATCH v6 21/21] timer: Always queue timers on the local CPU Date: Wed, 10 May 2023 09:28:17 +0200 Message-Id: <20230510072817.116056-22-anna-maria@linutronix.de> In-Reply-To: <20230510072817.116056-1-anna-maria@linutronix.de> References: <20230510072817.116056-1-anna-maria@linutronix.de> MIME-Version: 1.0 X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1765492349786592586?= X-GMAIL-MSGID: =?utf-8?q?1765492349786592586?= The timer pull model is in place so we can remove the heuristics which try to guess the best target CPU at enqueue/modification time. All non pinned timers are queued on the local CPU in the separate storage and eventually pulled at expiry time to a remote CPU. Originally-by: Richard Cochran (linutronix GmbH) Signed-off-by: Anna-Maria Behnsen --- v6: - Update TIMER_PINNED flag description. v5: - Move WARN_ONCE() in add_timer_on() into a previous patch - Fold crystallball magic related hunks into this patch v4: Update comment about TIMER_PINNED flag (heristic is removed) --- include/linux/timer.h | 14 ++++---------- kernel/time/timer.c | 42 ++++++++++++++++++++---------------------- 2 files changed, 24 insertions(+), 32 deletions(-) diff --git a/include/linux/timer.h b/include/linux/timer.h index 6f96661480dd..c39ae2ad0035 100644 --- a/include/linux/timer.h +++ b/include/linux/timer.h @@ -50,16 +50,10 @@ struct timer_list { * workqueue locking issues. It's not meant for executing random crap * with interrupts disabled. Abuse is monitored! * - * @TIMER_PINNED: A pinned timer will not be affected by any timer - * placement heuristics (like, NOHZ) and will always expire on the CPU - * on which the timer was enqueued. - * - * Note: Because enqueuing of timers can migrate the timer from one - * CPU to another, pinned timers are not guaranteed to stay on the - * initialy selected CPU. They move to the CPU on which the enqueue - * function is invoked via mod_timer() or add_timer(). If the timer - * should be placed on a particular CPU, then add_timer_on() has to be - * used. + * @TIMER_PINNED: A pinned timer will always expire on the CPU on which the + * timer was enqueued. When a particular CPU is required, add_timer_on() + * has to be used. Enqueue via mod_timer() and add_timer() is always done + * on the local CPU. */ #define TIMER_CPUMASK 0x0003FFFF #define TIMER_MIGRATING 0x00040000 diff --git a/kernel/time/timer.c b/kernel/time/timer.c index 1d8323fc76ee..44ea73cd8fa7 100644 --- a/kernel/time/timer.c +++ b/kernel/time/timer.c @@ -590,10 +590,13 @@ trigger_dyntick_cpu(struct timer_base *base, struct timer_list *timer) /* * We might have to IPI the remote CPU if the base is idle and the - * timer is not deferrable. If the other CPU is on the way to idle - * then it can't set base->is_idle as we hold the base lock: + * timer is pinned. If it is a non pinned timer, it is only queued + * on the remote CPU, when timer was running during queueing. Then + * everything is handled by remote CPU anyway. If the other CPU is + * on the way to idle then it can't set base->is_idle as we hold + * the base lock: */ - if (base->is_idle) + if (base->is_idle && timer->flags & TIMER_PINNED) wake_up_nohz_cpu(base->cpu); } @@ -941,17 +944,6 @@ static inline struct timer_base *get_timer_base(u32 tflags) return get_timer_cpu_base(tflags, tflags & TIMER_CPUMASK); } -static inline struct timer_base * -get_target_base(struct timer_base *base, unsigned tflags) -{ -#if defined(CONFIG_SMP) && defined(CONFIG_NO_HZ_COMMON) - if (static_branch_likely(&timers_migration_enabled) && - !(tflags & TIMER_PINNED)) - return get_timer_cpu_base(tflags, get_nohz_timer_target()); -#endif - return get_timer_this_cpu_base(tflags); -} - static inline void forward_timer_base(struct timer_base *base) { unsigned long jnow = READ_ONCE(jiffies); @@ -1103,7 +1095,7 @@ __mod_timer(struct timer_list *timer, unsigned long expires, unsigned int option if (!ret && (options & MOD_TIMER_PENDING_ONLY)) goto out_unlock; - new_base = get_target_base(base, timer->flags); + new_base = get_timer_this_cpu_base(timer->flags); if (base != new_base) { /* @@ -2181,8 +2173,14 @@ u64 get_next_timer_interrupt(unsigned long basej, u64 basem) */ } - /* We need to mark both bases in sync */ - base_local->is_idle = base_global->is_idle = is_idle; + /* + * base->is_idle information is required to wakeup a idle CPU when + * a new timer was enqueued. Only pinned timers could be enqueued + * remotely into a idle base. Therefore do maintain only + * base_local->is_idle information and ignore base_global->is_idle + * information. + */ + base_local->is_idle = is_idle; raw_spin_unlock(&base_global->lock); raw_spin_unlock(&base_local->lock); @@ -2212,13 +2210,13 @@ u64 get_next_timer_interrupt(unsigned long basej, u64 basem) void timer_clear_idle(void) { /* - * We do this unlocked. The worst outcome is a remote enqueue sending - * a pointless IPI, but taking the lock would just make the window for - * sending the IPI a few instructions smaller for the cost of taking - * the lock in the exit from idle path. + * We do this unlocked. The worst outcome is a remote pinned timer + * enqueue sending a pointless IPI, but taking the lock would just + * make the window for sending the IPI a few instructions smaller + * for the cost of taking the lock in the exit from idle + * path. Required for BASE_LOCAL only. */ __this_cpu_write(timer_bases[BASE_LOCAL].is_idle, false); - __this_cpu_write(timer_bases[BASE_GLOBAL].is_idle, false); /* Activate without holding the timer_base->lock */ tmigr_cpu_activate();