Received: by 2002:a05:7412:d8a:b0:e2:908c:2ebd with SMTP id b10csp2971344rdg; Mon, 16 Oct 2023 23:50:04 -0700 (PDT) X-Google-Smtp-Source: AGHT+IF76XVapwQ5SAjzzbbCGUlqwYv0yLh64gL14Hkk3Yf5FIfmWvNt8y8d+Sn5wFYb5bEUwobP X-Received: by 2002:a05:6a21:778d:b0:131:c760:2a0b with SMTP id bd13-20020a056a21778d00b00131c7602a0bmr1084351pzc.52.1697525404668; Mon, 16 Oct 2023 23:50:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1697525404; cv=none; d=google.com; s=arc-20160816; b=wYEUoD4MKfXKfS8J/DaNYZZIAPkMbPr5qt6JRhs+LX8r+5aa5IcJM73XNBCs66Njao /fDj8ZQx0vEHKL3BQMwrBTlHPDYtE5f/6XghC/ZXMU7Ky8Hp0i0iSs6ebdzks+3pMEcz I0R6aOfar35O3FNSIPA/T/ILEDWxDd6WAFM4kb0eMa3suZAkKD/bYWGeG+L4biGrx9VD TyDKbdnHq8GVAgD2rudJL8qWHLd7OgDNvv+xhjgDjjN+fFg1blDi6/ifOSI/reUlzMwb TCpXlwsd9rkis68Bs/13rZFODKUQg7H0HPTkt2tz0bOEPOhHL+ClvwZuUnlfUAJajyZb py0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:dkim-signature:dkim-signature:from; bh=/FE1gLbMogP0SwbL+MBx94k/MbhBH/aKzYuo6+Povrw=; fh=jPGFV3mZjSgRvcSbN2XZOC9XwfuCaG+9SM+69wXSI60=; b=fGVa1XOFMrdIw96802K6OuQQVqHVQbqV564YsjB6zIgjFYXP4AMAKK4mKawmWLBcsa iA9v7Qm6QkVVmVq8bzFiReaqChBXvIE9FVC0STEmb4bhiuTUum3D7DMkhC0o0grC2pLX qy/8GPFZHdl0e7QuoxpmyKYvSeWJqP3KmsmicZ29ld1ccxLPIlNefQfu2hfuXvW4cB87 LfCsiyc1PrXEL7p6ksYa/og+ib1yV6h8S4nMxn6JFan+L1IO2JBLxAmyikxl1qpkXLXy 532qneMBY2VGeB6W5LxY+8YGVwaQ7iz3fOwQ7TXLB00Oo7/kLF8me+0AWJaTmqqSQRNs cdCg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=boGkJasY; dkim=neutral (no key) header.i=@linutronix.de; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from howler.vger.email (howler.vger.email. [23.128.96.34]) by mx.google.com with ESMTPS id m9-20020a17090ab78900b00273dfe0741csi7346500pjr.90.2023.10.16.23.50.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 16 Oct 2023 23:50:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) client-ip=23.128.96.34; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=boGkJasY; dkim=neutral (no key) header.i=@linutronix.de; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 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 (depot.vger.email [IPv6:2620:137:e000::3:0]) by howler.vger.email (Postfix) with ESMTP id 49A2880B2D42; Mon, 16 Oct 2023 23:50:02 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at howler.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234518AbjJQGty (ORCPT + 99 others); Tue, 17 Oct 2023 02:49:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39492 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234543AbjJQGtw (ORCPT ); Tue, 17 Oct 2023 02:49:52 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CE51DEA for ; Mon, 16 Oct 2023 23:49:49 -0700 (PDT) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1697525387; 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=/FE1gLbMogP0SwbL+MBx94k/MbhBH/aKzYuo6+Povrw=; b=boGkJasYeL3vD1USUD2ST/X8aISjFqsQ2P6gmV+YCXjR6n37kHLuwumy/X1lFlmQ8Px3S7 DOjYfUOpFBWKWmY7DTtfL9mRuLEghMQWBOXXy3rpTy1b5ePglNN9ZRm3Sdj8osXGamLZ9E lH3F82iyKkIoLenCnjAMdDb5zWF+UTscm8y4ZWMyOFfPHVhaaEJ/0J6GoM1/zr/Usuffuk KchVdlzOK4PgAUt/Sc65IMzCQgEhZuFD7bfRxD+1DAdxSlT9CISmifZDH2QCHCW9+NlJrk WXF3uLsajYYPchcxuooqWLlgw5KXvgKkbcV289kFlZfchCfaOHTsstYu3d1AJg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1697525387; 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=/FE1gLbMogP0SwbL+MBx94k/MbhBH/aKzYuo6+Povrw=; b=V+n9yJBoAbeGvpkx2NrV+eMTB5AtBHodwhqZF4scXV1QNZgoECqA04G36MK4/RNbXNyDxv KlaH48+l6gYuQEBg== To: paulmck@kernel.org Cc: John Stultz , Tetsuo Handa , Stephen Boyd , LKML , Sebastian Andrzej Siewior , x86@kernel.org Subject: Re: [PATCH] clocksource: disable irq when holding watchdog_lock. In-Reply-To: References: <80ff5036-8449-44a6-ba2f-0130d3be6b57@I-love.SAKURA.ne.jp> <878r826xys.ffs@tglx> Date: Tue, 17 Oct 2023 08:49:46 +0200 Message-ID: <8734y97ng5.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on howler.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (howler.vger.email [0.0.0.0]); Mon, 16 Oct 2023 23:50:02 -0700 (PDT) On Mon, Oct 16 2023 at 16:03, Paul E. McKenney wrote: > On Mon, Oct 16, 2023 at 11:47:55PM +0200, Thomas Gleixner wrote: >> That said, this whole clocksource watchdog mess wants a proper >> overhaul. It has become a pile of warts and duct tape by now and after >> staring at it long enough there is no real reason to run it in a timer >> callback anymore. It just can move into delayed work and the whole >> locking problem can be reduced to the clocksource_mutex and some well >> thought out atomic operations to handle the mark unstable case. But >> that's a different story and not relevant for curing the problem at >> hand. > > Moving the code to delayed work seems quite reasonable. > > But Thomas, you do understand that the way things have been going for > the clocksource watchdog, pushing it out to delayed work will no doubt > add yet more hair on large busy systems, right? Yeah, yeah, I know, > delayed work shouldn't be any worse than ksoftirqd. The key word of > course being "shouldn't". ;-) Yes, I'm aware of that. I still think it's worth at least to try it. Thanks, tglx