From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A200E33F370; Tue, 7 Apr 2026 18:01:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775584906; cv=none; b=OPbYWPaCxt9fyXfFHXl2XGV8PhuloBhIwOzvTxW20fFfI6HgMVfTcGg0AzCPw59/WlskBf/sp9EqZ9t/F0XWfJC08FIFw0uBlANoIqYYaOrt0mMjTbp8D+quuztdSlIWxPPYbTEl1wo6M+Y/WDQOgpTPbGNfFNXD7GVadb14ghc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775584906; c=relaxed/simple; bh=6B+bB4wDwu6y52UEp2vUDg3kQcT5fRjCxX/e9OhjKYQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=fDcrT/Vm+Pnt18Dl0mN+IoeLXXuQDxsfBY9GG5wQn80Sv68ASFpLflbV9ITALug6F7lw9kHpXu9AsDSVXrifP1VfrtuLkB5qySPS8IS8gbbwXiiK2A3cYSbtNB/Nelhpr30E/nqoqMIEAyWUYOeDr/yU9j32RLoKXUIZmTDSSAs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ffncIQTB; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ffncIQTB" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5ECE8C19424; Tue, 7 Apr 2026 18:01:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1775584906; bh=6B+bB4wDwu6y52UEp2vUDg3kQcT5fRjCxX/e9OhjKYQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=ffncIQTB9uPSPzX+Hl67zcMc6bar4Dmd29wGTqpWwOeGOO4SU1YQ6w0FJYlm5PLeO fgb/hVw5sv/eL6LG/wa2UmQxRzt2MVjRl+LDbJq4AKYtN45D3Y6b1Xa8dUkSSxkwPZ 8IIMG/iWcbW7ILFIU/Hy7qbxpuCy61KpvfMjemLmpYNLT4JLCROnyPxgh35IXVE5e0 CrzxrJWUq3nI+ByPHY2xTfuMpKfmLeShgRWSg3reO1A3ddBI6rfxbDA335mYN/KA1g VEhzOrCmRP6zyYfLam0a05rOF06NG89aw/mchas8rn5jGzUuB/GsJMNazR1DSapjPv dcpPxlH/SQl+w== From: Thomas Gleixner To: Frederic Weisbecker Cc: LKML , Calvin Owens , Peter Zijlstra , Anna-Maria Behnsen , Ingo Molnar , John Stultz , Stephen Boyd , Alexander Viro , Christian Brauner , Jan Kara , linux-fsdevel@vger.kernel.org, Sebastian Reichel , linux-pm@vger.kernel.org, Pablo Neira Ayuso , Florian Westphal , Phil Sutter , netfilter-devel@vger.kernel.org, coreteam@netfilter.org Subject: Re: [patch 01/12] clockevents: Prevent timer interrupt starvation In-Reply-To: <87tstm4uss.ffs@tglx> References: <20260407083219.478203185@kernel.org> <20260407083247.562657657@kernel.org> <87tstm4uss.ffs@tglx> Date: Tue, 07 Apr 2026 20:01:42 +0200 Message-ID: <87ldey4pkp.ffs@tglx> Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Tue, Apr 07 2026 at 18:08, Thomas Gleixner wrote: > On Tue, Apr 07 2026 at 16:00, Frederic Weisbecker wrote: > As I had to introduce the flag and prevent the other scenraio I just > consolidated everything into one code path. Just for the record. This whole -ETIME handling is restricted to HPET like devices where the hardware people decided it's a brilliant idea to build a 'equal' comparator and then followed up by making the write posted to reduce the costs of the write. The original direct write was already flawed vs. NMI/SMI, but the delayed commit into the comparator made it insanely broken. AFAICT that's a handful devices in the zoo of clockevent IPs the kernel supports, so I'm really not too worried about the impact of this change. Any sane hardware will never hit that code path so no point for optimizing for it. Thanks, tglx