From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 327FDC433B4 for ; Fri, 14 May 2021 19:29:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 11A0D61454 for ; Fri, 14 May 2021 19:29:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232882AbhENTat (ORCPT ); Fri, 14 May 2021 15:30:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35276 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231869AbhENTao (ORCPT ); Fri, 14 May 2021 15:30:44 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D71BFC061574 for ; Fri, 14 May 2021 12:29:30 -0700 (PDT) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1621020567; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=BUCRh6+JO6hwPoznRg0DikeObEjzSgPqiFp6VBNC0BA=; b=upcs4dh8Cfn0LxB0CTZjFaafR09fumaQIKcDs80pPzNcvy9sRYs+QeqSJjYbaIP1VclrR5 ao17N6mth3Saiua0gww57C/243IWyhYoH4/NYRI5vWIc86WFwSemNuQjSbZmuRWI47g5a2 DSLyAWHQwdl7C+vNAVRGABr4Nuf/W82ZqlxroJqxI/afArziPy++nUtR+8sulJRrkjEHUp 0vI8xGBE0RmLGDxjx0f3xd4xinATbA2ktpweKOSqrjsDi5hO4XEiMOumk8OxGnZqsJ8JI9 piDaNku04g7njiGaDAkjX0H8sI5Zh5Rit/nem/UXW1MPeiq7X/QJQnSRKIsZxA== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1621020567; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=BUCRh6+JO6hwPoznRg0DikeObEjzSgPqiFp6VBNC0BA=; b=hrOKMEb1Sx2wT7jVWxmi4G8D8GWa3B/SNyLUYI++NCjn36kmbiAwWI2E1jYa3B0646MvkE KtgYa6Iv/F/itEDQ== To: Peter Zijlstra Cc: Lorenzo Colitti , Greg KH , Maciej =?utf-8?Q?=C5=BBenczykowski?= , Ingo Molnar , Anna-Maria Behnsen , lkml , mikael.beckius@windriver.com, Maciej =?utf-8?Q?=C5=BBenczykowski?= , Will Deacon Subject: Re: [PATCH] hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns() In-Reply-To: References: <87r1jbv6jc.ffs@nanos.tec.linutronix.de> <87eef5qbrx.ffs@nanos.tec.linutronix.de> <87v989topu.ffs@nanos.tec.linutronix.de> Date: Fri, 14 May 2021 21:29:27 +0200 Message-ID: <875yzl3yi0.ffs@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 26 2021 at 14:25, Peter Zijlstra wrote: > On Mon, Apr 26, 2021 at 11:40:46AM +0200, Peter Zijlstra wrote: >> There is an unfortunate amount of duplication between >> hrtimer_force_reprogram() and hrtimer_reprogram(). The obvious cleanups >> don't work however :/ Still, does that in_hrtirq optimization make sense >> to have in force_reprogram ? No. It need's to be in hrtimer_programm().