hrtimers: Unconditionally update target CPU base after offline timer migration

When testing softirq based hrtimers on an ARM32 board, with high resolution
mode and NOHZ inactive, softirq based hrtimers fail to expire after being
moved away from an offline CPU:

CPU0 CPU1
hrtimer_start(..., HRTIMER_MODE_SOFT);
cpu_down(CPU1) ...
hrtimers_cpu_dying()
// Migrate timers to CPU0
smp_call_function_single(CPU0, returgger_next_event);
retrigger_next_event()
if (!highres && !nohz)
return;

As retrigger_next_event() is a NOOP when both high resolution timers and
NOHZ are inactive CPU0's hrtimer_cpu_base::softirq_expires_next is not
updated and the migrated softirq timers never expire unless there is a
softirq based hrtimer queued on CPU0 later.

Fix this by removing the hrtimer_hres_active() and tick_nohz_active() check
in retrigger_next_event(), which enforces a full update of the CPU base.
As this is not a fast path the extra cost does not matter.

[ tglx: Massaged change log ]

Fixes: 5c0930ccaad5 ("hrtimers: Push pending hrtimers away from outgoing CPU earlier")
Co-developed-by: Frederic Weisbecker <frederic@kernel.org>
Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
Signed-off-by: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/all/20250805081025.54235-1-wangxiongfeng2@huawei.com

authored by Xiongfeng Wang and committed by Thomas Gleixner e895f8e2 76eeb9b8

+3 -8
+3 -8
kernel/time/hrtimer.c
··· 787 787 * of the next expiring timer is enough. The return from the SMP 788 788 * function call will take care of the reprogramming in case the 789 789 * CPU was in a NOHZ idle sleep. 790 + * 791 + * In periodic low resolution mode, the next softirq expiration 792 + * must also be updated. 790 793 */ 791 - if (!hrtimer_hres_active(base) && !tick_nohz_active) 792 - return; 793 - 794 794 raw_spin_lock(&base->lock); 795 795 hrtimer_update_base(base); 796 796 if (hrtimer_hres_active(base)) ··· 2295 2295 &new_base->clock_base[i]); 2296 2296 } 2297 2297 2298 - /* 2299 - * The migration might have changed the first expiring softirq 2300 - * timer on this CPU. Update it. 2301 - */ 2302 - __hrtimer_get_next_event(new_base, HRTIMER_ACTIVE_SOFT); 2303 2298 /* Tell the other CPU to retrigger the next event */ 2304 2299 smp_call_function_single(ncpu, retrigger_next_event, NULL, 0); 2305 2300