Re: [patch 5/5] clocksource: Rewrite watchdog code completely
Jiri Wiesner <[email protected]>
| Newsgroups | org.kernel.vger.linux-parisc,org.kernel.vger.linux-kernel,org.kernel.vger.linux-mips |
|---|---|
| Message-ID | <abFqNsVLKmhc6aLY@incl> |
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 <[email protected]> in the next version of the patchset. -- Jiri Wiesner SUSE Labs