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 AD22FD531 for ; Fri, 3 Apr 2026 19:00:59 +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=1775242859; cv=none; b=eRhZtGYclO7E1GGMXo3JDbHdrVIRF2Rn6Mdig9W5rgYa53tR7Rq2RNkA6VHeL1IMoFo/UTim9t6aE/5B99EFShx/V+LCtZ0zE4aFBSyH7UsHdV2haXXunnSyZv3H6eB8W2Q1KRoNQib2zBBRng6XjJorlnnrUXaXrRElhMjDI3w= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775242859; c=relaxed/simple; bh=OtLqfi9DtqPV4eGGRBKNj8gxMSsR1aUdv/lxA5fO/hM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=JQCFvMmcHOOwjm0iLR01XWwI7VzRQIwcG19poZxEheUghuJgYfhWUC6GtbedWBPl/cY1ljXKIs9vd3oC7A56Tj+906FTNDNxIruWK9Vr/ZEsPUNsJVhBNLsU94jV73soWikXfViyI58ybi7BX3+1CQHufxHAu6brtdCpc1Hvims= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=DFtv2pjV; 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="DFtv2pjV" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6A83FC4CEF7; Fri, 3 Apr 2026 19:00:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1775242859; bh=OtLqfi9DtqPV4eGGRBKNj8gxMSsR1aUdv/lxA5fO/hM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=DFtv2pjVMvAOuS8auEb98uICsT0DqDVRoNJCGRAwrRAQAxyk8yozUQhKMmsdmmG6j ho44Xb0tK5YutJqrgyBdUkgeSN5ojPk073Y1HlkUgLVqqD8Eiy92TA33vERTwl8zHH 4BBhOlgFi7/4zi1NfxVAXjzCjc3dFCgLKgq298cZGnA0ZvwXoma+aBbcXMVcukTyev /5oLQBah5SHDmd1Yku6NK9NjwZDuOWMFhlevlO+U+/v1g0okkLzhE4k3KkDf+9+VDv HhYwfr/MR9I1PPtC2EiSefzrga9PMO6pL9PjBo+pblmZhSkZ7/dMl7wTmY+5GarkwS QHUCcxl0tqAKw== From: Thomas Gleixner To: Calvin Owens Cc: Borislav Petkov , Petr Mladek , linux-kernel@vger.kernel.org, arighi@nvidia.com, yaozhenguo1@gmail.com, tj@kernel.org, feng.tang@linux.alibaba.com, lirongqing@baidu.com, realwujing@gmail.com, hu.shengming@zte.com.cn, dianders@chromium.org, joel.granados@kernel.org, Ingo Molnar , Peter Zijlstra , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Valentin Schneider , Frederic Weisbecker , Anna-Maria Behnsen , x86@kernel.org Subject: Re: [PATCH] clockevents: Prevent timer interrupt starvation In-Reply-To: References: <87v7ejetl1.ffs@tglx> <875x6a913n.ffs@tglx> <20260401163435.GGac1JG42tWmsCKL37@fat_crate.local> <87jyup70ka.ffs@tglx> <87bjg06r7t.ffs@tglx> Date: Fri, 03 Apr 2026 21:00:55 +0200 Message-ID: <87zf3j6f88.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Fri, Apr 03 2026 at 08:58, Calvin Owens wrote: > On Friday 04/03 at 16:41 +0200, Thomas Gleixner wrote: >> I'm an idiot. When I polished the patch up, I dropped the hunks which >> clear the flag in the interrupt handler and tired brain did not notice >> despite checking five times in a row. Updated version below. > > That did it, both AMD machines survive the reproducer and are well > behaved afterwards. Thank you and sorry for the nuisance. > If you like: > > Tested-By: Calvin Owens I will probably post a slightly different version similar to the one I sent in the reply to Peter and if you have time then I would appreciate a tested-by on that final to be polished version. Btw, I'm really curious how you deduced the reproducer from systemd code. I assume you figured somehow out which program triggered the behaviour and then inspected the source to find something fishy. Can you provide a pointer to the code in question? If they really do what your reproducer does, then this code needs to be fixed too :) Thanks, tglx