| From | Thomas Gleixner <> | Subject | Re: [PATCH 09/15] tick: Move broadcast cancellation up to CPUHP_AP_TICK_DYING | Date | Thu, 25 Jan 2024 10:38:36 +0100 |
| |
On Wed, Jan 24 2024 at 18:04, Frederic Weisbecker wrote: > The broadcast shutdown code is executed through a random explicit call > within stop machine from the outgoing CPU. > > However The tick broadcast is a midware between the tick callback and
s/The/the/
> the clocksource, therefore it makes more sense to shut it down after the > tick callback and before the clocksource drivers. > > Move it instead to the common tick shutdown CPU hotplug state where > related operations can be ordered from highest to lowest level. > > Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
|