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;
From:   Thomas Gleixner <tglx@linutronix.de>
To:     paulmck@kernel.org
Cc:     linux-kernel@vger.kernel.org, john.stultz@linaro.org,
        sboyd@kernel.org, corbet@lwn.net, Mark.Rutland@arm.com,
        maz@kernel.org, kernel-team@meta.com, neeraju@codeaurora.org,
        ak@linux.intel.com, feng.tang@intel.com, zhengjun.xing@intel.com,
        Waiman Long <longman@redhat.com>,
        John Stultz <jstultz@google.com>
Subject: Re: [PATCH clocksource 5/6] clocksource: Suspend the watchdog
 temporarily when high read latency detected
In-Reply-To: <20230111175056.GW4028633@paulmck-ThinkPad-P17-Gen-1>
References: <20230105010429.GA1773522@paulmck-ThinkPad-P17-Gen-1>
 <20230105010701.1773895-5-paulmck@kernel.org> <87r0w1ia65.ffs@tglx>
 <20230111175056.GW4028633@paulmck-ThinkPad-P17-Gen-1>
Date:   Wed, 11 Jan 2023 22:19:50 +0100
Message-ID: <87wn5sepl5.ffs@tglx>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

On Wed, Jan 11 2023 at 09:50, Paul E. McKenney wrote:
> On Wed, Jan 11, 2023 at 12:26:58PM +0100, Thomas Gleixner wrote:
> Yes, if a system was 100% busy forever, this patch would suppress these
> checks.  But 100% busy forever is not the common case, due to thermal
> throttling and to security updates if nothing else.
>
> With all that said, is there a better way to get the desired effects of
> this patch?

Sane hardware?