From: Jiri Wiesner <jwiesner@suse.de>
To: Thomas Gleixner <tglx@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
John Stultz <jstultz@google.com>,
Waiman Long <longman@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
x86@kernel.org, "Gautham R. Shenoy" <gautham.shenoy@amd.com>,
Daniel J Blueman <daniel@quora.org>,
Scott Hamilton <scott.hamilton@eviden.com>,
Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org
Subject: Re: [patch 5/5] clocksource: Rewrite watchdog code completely
Date: Wed, 11 Mar 2026 14:12:22 +0100 [thread overview]
Message-ID: <abFqNsVLKmhc6aLY@incl> (raw)
In-Reply-To: <87y0k21vro.ffs@tglx>
On Sun, Mar 08, 2026 at 11:05:31AM +0100, Thomas Gleixner wrote:
> On Wed, Feb 25 2026 at 19:13, Jiri Wiesner wrote:
> > On Sat, Jan 24, 2026 at 12:18:01AM +0100, Thomas Gleixner wrote:
> >> To address this and bring back sanity to the watchdog, rewrite the code
> >> completely with a different approach:
> >>
> >> 1) Restrict the validation against a reference clocksource to the boot
> >> CPU, which is usually the CPU/Socket closest to the legacy block which
> >> contains the reference source (HPET/ACPI-PM timer).
> >
> > The UEFI picks the boot CPU so the kernel does not have control over
> > that. On the other hand, I think the CPU that is connected to the
> > southbridge chip (by DMI or PCIe) will be selected in the majority of
> > UEFI implementations.
>
> Picking a remote node CPU would be insane, but yes BIOSes are insane by
> definition.
Yes, I was mostly just being paranoid. Please include:
Reviewed-by: Jiri Wiesner <jwiesner@suse.de>
in the next version of the patchset.
--
Jiri Wiesner
SUSE Labs
next prev parent reply other threads:[~2026-03-11 13:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 23:17 [patch 0/5] clocksource: Rewrite clocksource watchdog and related cleanups Thomas Gleixner
2026-01-23 23:17 ` [patch 1/5] parisc: Remove unused clocksource flags Thomas Gleixner
2026-01-24 8:40 ` Helge Deller
2026-01-23 23:17 ` [patch 2/5] MIPS: Dont select CLOCKSOURCE_WATCHDOG Thomas Gleixner
2026-01-24 22:28 ` Maciej W. Rozycki
2026-01-26 9:10 ` Thomas Gleixner
2026-01-23 23:17 ` [patch 3/5] x86/tsc: Handle CLOCK_SOURCE_VALID_FOR_HRES correctly Thomas Gleixner
2026-01-23 23:17 ` [patch 4/5] clocksource: Dont use non-continuous clocksources as watchdog Thomas Gleixner
2026-01-23 23:18 ` [patch 5/5] clocksource: Rewrite watchdog code completely Thomas Gleixner
2026-02-02 6:45 ` Daniel J Blueman
2026-02-02 11:27 ` Thomas Gleixner
2026-02-15 12:18 ` Daniel J Blueman
2026-02-23 13:53 ` Thomas Gleixner
2026-03-08 9:53 ` Thomas Gleixner
2026-03-15 14:59 ` Daniel J Blueman
2026-03-17 9:01 ` Thomas Gleixner
2026-03-18 14:10 ` Daniel J Blueman
2026-03-19 20:31 ` Thomas Gleixner
2026-03-20 2:21 ` Daniel J Blueman
2026-02-25 18:13 ` Jiri Wiesner
2026-03-08 10:05 ` Thomas Gleixner
2026-03-11 13:12 ` Jiri Wiesner [this message]
2026-03-09 15:43 ` Borislav Petkov
2026-03-11 7:58 ` 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=abFqNsVLKmhc6aLY@incl \
--to=jwiesner@suse.de \
--cc=daniel.lezcano@linaro.org \
--cc=daniel@quora.org \
--cc=deller@gmx.de \
--cc=gautham.shenoy@amd.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-parisc@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=tglx@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.