On 11/5/2026 10:00 PM, Frederic Weisbecker wrote:
Between CPUHP_TEARDOWN_CPU and CPUHP_AP_OFFLINE, stop_machine executes all the teardown callbacks while stopping all CPUs in the system. This doesn't mix-up well with running RT or isolated tasks. In order to transition smoothly from global stop_machine to finer grained synchronization between teardown callbacks and the other CPUs, a new stop machine post function has been introduced to be executed after the main one with IRQs still disabled while other CPUs can exit stop_machine(). The teardown callback here simply performs timer and IRQ disablement, both of which can run concurrently with other CPUs. Move it to post stop_machine() accordingly. Signed-off-by: Frederic Weisbecker <[email protected]> --- kernel/cpu.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/cpu.c b/kernel/cpu.c index 93b8498e26c4..b49b67ef5ecb 100644
I am unable to correlate the commit message with the change and could not find the rest of the series on lore to get more context.
Regards, Naman
--- a/kernel/cpu.c +++ b/kernel/cpu.c @@ -1275,7 +1275,7 @@ void clear_tasks_mm_cpumask(int cpu) static int take_cpu_down(void *_param) { struct cpuhp_cpu_state *st = this_cpu_ptr(&cpuhp_state); - enum cpuhp_state target = max((int)st->target, CPUHP_AP_TI_GP_TIMER_STARTING); + enum cpuhp_state target = max((int)st->target, CPUHP_AP_HYPERV_TIMER_STARTING); int err, cpu = smp_processor_id();/* Ensure this CPU doesn't handle any more interrupts. */@@ -1303,7 +1303,7 @@ static int take_cpu_down_post(void *_param) enum cpuhp_state target = max((int)st->target, CPUHP_AP_OFFLINE); int cpu = smp_processor_id();- WARN_ON(st->state != CPUHP_AP_TI_GP_TIMER_STARTING);+ WARN_ON(st->state != CPUHP_AP_HYPERV_TIMER_STARTING); /* * Invoke the former CPU_DYING callbacks. DYING must not fail! */
