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 C8CADC433E0 for ; Mon, 1 Mar 2021 09:14:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 80B4964E22 for ; Mon, 1 Mar 2021 09:14:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233658AbhCAJOB (ORCPT ); Mon, 1 Mar 2021 04:14:01 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:57882 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233009AbhCAJN7 (ORCPT ); Mon, 1 Mar 2021 04:13:59 -0500 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1614589997; 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=eaN0GLkpvxq4H2WhMZJuMDc0+wEhRVfWSwLjNj11LuQ=; b=121e2GMlQ72jXhYmjUf15Hdbe6efchPOnDmntbthSNGfOUOjPfBLZiKHCmfGbGYbBb2vWs kOlT6d3CnZNcVTzM6Bod/NNlBkRNO/KR6hhchZWyhPALp1NDt6u3Qecq7J2dfZ1XDaHKYE L2jYuZwjbdJ0BuY1HgNWMp6KH30aqQf2hqn2x0EhDumWvmUd3DpSDwOaN/ondeM6zXDfQe xQ910hwVg32V1k0knNjOpp/om+456xfZqUTfYIsHZRrEEVdc0g8abU4A1lDDFSmVCteVwt quKXMHdPqMcAuaxIe29C2s9mc/9EHA3nnTtwkmuxAQmg4WP8Jf/43GuB8tUB4A== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1614589997; 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=eaN0GLkpvxq4H2WhMZJuMDc0+wEhRVfWSwLjNj11LuQ=; b=Ei1why0BXayLBKwouqVb+nsd81oTknwh7ZuguNBV9QkkPCD0Hd+Aann7VaoN3RD9MF0lUD limwh7JoVumBcLAg== To: Mikael Beckius , anna-maria@linutronix.de Cc: linux-kernel@vger.kernel.org, mikael.beckius@windriver.com Subject: Re: Sv: Sv: [PATCH] hrtimer: Interrupt storm on clock_settime In-Reply-To: <20210225111814.8383-1-mikael.beckius@windriver.com> References: <20210225111814.8383-1-mikael.beckius@windriver.com> Date: Mon, 01 Mar 2021 10:13:17 +0100 Message-ID: <87k0qrtexe.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Micke, On Thu, Feb 25 2021 at 12:18, Mikael Beckius wrote: >> The proposed change breaks the reprogramming logic. To keep it working >> cpu_base::*expires_next is only updated by hrtimer_reprogram() and >> hrtimer_interrupt(). I will send you a patch for testing in reply to this >> thread. The patch is compile tested only. >> > Ok. I kind of guessed that would be the response as I noticed a similar comment > during the review of the original patch which introduced the softirq_expires_next > logic. Anyway it seemed logical to update softirq_expires_next > when updating softirq_next_timer. yes it seems logical to do that, but unfortunately the logic there is a bit twisted and could do with some deobfuscation. Thanks, tglx