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 E4132402453 for ; Tue, 24 Mar 2026 17:24:19 +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=1774373060; cv=none; b=c8BwjKi3dCaUWM6cRepaw//KgY+gJ5eObtBOb245b6XZ2UOcCBe86B9wj0sYu8a7nrDz1wIxxoBvQmW+/xYx2X8hyjdrNl2tik5VIGlCwO8sN/CZJKD0EDrHokEhlabLpTfULletxxkile1sJNVuLcpo4VZ3TQwmTRS84yWhLT0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774373060; c=relaxed/simple; bh=ssc0k8zVVSpMQ1qt4pTHX54GCY7lKxgaq/w0I5ByNOc=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=u1iVQeWBAI0G3FxH1cjRlndlqcQhqcZicUzNl64FxYIp5IOdyFhH9ELOj7dXehCj34SVO0wA9c9NALRyObo0B1FkzXczCndz2RcMtK/s0WO5SGBLluxlEzMYIs1+Ya+//RTnUGeqd9Vu/Jdd/9stoTUBm8WJDVo1Y89dadWAC6E= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=n1LzuN7g; 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="n1LzuN7g" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C2D5DC19424; Tue, 24 Mar 2026 17:24:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1774373059; bh=ssc0k8zVVSpMQ1qt4pTHX54GCY7lKxgaq/w0I5ByNOc=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=n1LzuN7gjAhaqCFTJrxNADIAayrdBZh6rU9RMa+Y+4wzAy6fIYsMRY6hVyf9DKlax LoZ4znb5n+FBYugm31bc4g+Xn7LHahcgjYuUGnA1UCAjkXhEfIcER9dyyc1SCTYuv9 Xnwqkl5xLT8eAlNTYqieURAw21ONwLgnanKBtiNCEwDs5o8VMrxm80G39mZw4J/mmv j1j+JsH10ONvEUloHCBpcBIxQg50En2/BHpLVrWnfMbTmhFeGP4vuQzmYFURk/eQJy gy0Ps6RzU6Yj0JtItT5t1E0HIdxcKq+e2rpqBVB7UoC6Vm4Tt1AJB2/L71NVSlauQA Ci79tjb/4qdpQ== From: Thomas Gleixner To: Michael Kelley , 'LKML' Cc: 'Anna-Maria Behnsen' , 'John Stultz' , 'Stephen Boyd' , 'Daniel Lezcano' , 'Juri Lelli' , 'Vincent Guittot' , 'Dietmar Eggemann' , 'Steven Rostedt' , 'Ben Segall' , 'Mel Gorman' , 'Valentin Schneider' , "x86@kernel.org" , 'Peter Zijlstra' , 'Frederic Weisbecker' , 'Eric Dumazet' Subject: RE: [patch 19/48] clockevents: Provide support for clocksource coupled comparators In-Reply-To: References: <20260224163022.795809588@kernel.org> <20260224163430.010425428@kernel.org> <87v7emgrd5.ffs@tglx> <002301dcbb24$4825b600$d8712200$@zohomail.com> Date: Tue, 24 Mar 2026 18:24:16 +0100 Message-ID: <87cy0tgmyn.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 Tue, Mar 24 2026 at 03:37, Michael Kelley wrote: > This approach is not as general as Peter's, but it covers the Hyper-V timer > case, and is simpler. The cost is an extra memory reference in > arch_inlined_clockevent_set_next_coupled(). arch/x86/Kconfig can continue Which can be avoided with a runtime_const if the decision between hyperv timer and tscdeadline timer happens before either of them registered the clockevent and does not change later on. Thanks, tglx