From: Thomas Gleixner <tglx@linutronix.de>
To: paulmck@kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Daniel J Blueman <daniel@quora.org>,
John Stultz <jstultz@google.com>,
Waiman Long <longman@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
Stephen Boyd <sboyd@kernel.org>,
Scott Hamilton <scott.hamilton@eviden.com>
Subject: Re: clocksource: Reduce watchdog readout delay limit to prevent false positives
Date: Sat, 20 Dec 2025 09:38:31 +0100 [thread overview]
Message-ID: <87qzspa6pk.ffs@tglx> (raw)
In-Reply-To: <308f260b-83c6-402e-9756-017be125bb44@paulmck-laptop>
On Fri, Dec 19 2025 at 16:18, Paul E. McKenney wrote:
> One might naively hope that the HPETs in a given system could synchronize
> themselves so that each CPU could read the HPET nearest it instead of
> everyone reading CPU 0's HPET. Or that some other means would allow
> reasonable access times. Hey, I can dream, can't I?
Sounds more like a nightmare TBH.
next prev parent reply other threads:[~2025-12-20 8:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 17:21 clocksource: Reduce watchdog readout delay limit to prevent false positives Thomas Gleixner
2025-12-18 0:48 ` Paul E. McKenney
2025-12-19 10:13 ` Thomas Gleixner
2025-12-20 0:18 ` Paul E. McKenney
2025-12-20 8:18 ` Thomas Gleixner
2025-12-22 5:50 ` Paul E. McKenney
2025-12-20 8:37 ` Thomas Gleixner
2025-12-20 16:39 ` Paul E. McKenney
2025-12-20 8:38 ` Thomas Gleixner [this message]
2025-12-20 16:35 ` Paul E. McKenney
2025-12-22 5:50 ` Paul E. McKenney
2025-12-23 0:27 ` Waiman Long
2026-01-21 10:37 ` [tip: timers/urgent] " tip-bot2 for Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87qzspa6pk.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=daniel@quora.org \
--cc=dave.hansen@linux.intel.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=sboyd@kernel.org \
--cc=scott.hamilton@eviden.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox