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 9FA0532573F for ; Mon, 27 Apr 2026 15:08:33 +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=1777302513; cv=none; b=GsMj3S4fUvjIMyryJZ8SAW3oSrsDp491oskkRkh4lseFTulRX0IvzzL3P/S7DngOLRezyQnRtuP5ce5KqnEAxTfGhM+e4orUuNg0ua1aJ6vKqMBs/KwQ4dLW2JK4O1/nDGhYZ7odkb1IZmllyPADAkSBC1erSPfOqORmcBQSfQM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777302513; c=relaxed/simple; bh=IW6mnfRdLmMY8raENcKSaRCum2r0bE97/MofHK21gYk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=GOltCESHPr2/Xzo3/Kzrl8USPjwXhNI45iBrWVt07KuKmO6eY5pDtaR87zDy3CXGZ1y0WzCrUaddrCyrSSsiBJVoz7uuLrwuhXUlYoi2nXqe09n4/VexOO6qHja0i1TxnqofVjBw1zYMJ09wxBRDkxDLl2r7MPDWa53zLON5HK4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Qs4AhO1A; 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="Qs4AhO1A" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A6C5AC19425; Mon, 27 Apr 2026 15:08:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1777302513; bh=IW6mnfRdLmMY8raENcKSaRCum2r0bE97/MofHK21gYk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Qs4AhO1A9BVxau+uZRO7DLqrPO1uD3Q6ZU8haXckIRjX/XIV9HfAM8+fawrr4qHcS XEgAW2Qt+hYQM/Ns1gHDJVWpQ91f3iJz7Hx+69EhP8tscmYF1uGvLkWGr5dhIqsech J0vO+GbM6jHqPFDuShpA0Zi2MopHpAflZ1n/XVWE/y0BFNHlO6RiUiBtqWKLPH5ctr kHmpFGaPOFGLlZ47UL1KGcFnhX+jtFW42Tn3ZKRtYa1BExgjKw3dbGTz07oApXUtwI 9T0Xjdg+gTLmIZkAHz06wbe2HW7Un2VgDV4rIeTP47sMG+vh5cunKMxsi6VyVPnvuG M5PraN9OYE+Wg== From: Thomas Gleixner To: Zhan Xusheng Cc: linux-kernel@vger.kernel.org, Zhan Xusheng Subject: Re: [PATCH] clockevents: Reset next_event_forced in the coupled programming path In-Reply-To: <20260427092824.48335-1-zhanxusheng@xiaomi.com> References: <20260427092824.48335-1-zhanxusheng@xiaomi.com> Date: Mon, 27 Apr 2026 17:08:29 +0200 Message-ID: <87eck0zbiq.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 Mon, Apr 27 2026 at 17:28, Zhan Xusheng wrote: > All successful event programming paths in clockevents_program_event() > reset next_event_forced to zero, except the clockevent_set_next_coupled() > path which was added before the starvation prevention mechanism. > > Add the missing reset for consistency. What for? It never reaches the point where it sets or checks that next_event_forced bit. Your AI slop is clearly not getting it.