hrtimer: Avoid pointless reprogramming in __hrtimer_start_range_ns()

Much like hrtimer_reprogram(), skip programming if the cpu_base is running
the hrtimer interrupt.

Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Thomas Gleixner <tglx@kernel.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Juri Lelli <juri.lelli@redhat.com>
Reviewed-by: Thomas Gleixner <tglx@kernel.org>
Link: https://patch.msgid.link/20260224163429.069535561@kernel.org

diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c
index 860af7a584289aee8ab382f5de2c05aa72083724..3088db419aa663203f0d3cd1df308265778f9499 100644 (file)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1269,6 +1269,14 @@ static int __hrtimer_start_range_ns(struct hrtimer *timer, ktime_t tim,
        }
 
        first = enqueue_hrtimer(timer, new_base, mode);
+
+       /*
+        * If the hrtimer interrupt is running, then it will reevaluate the
+        * clock bases and reprogram the clock event device.
+        */
+       if (new_base->cpu_base->in_hrtirq)
+               return false;
+
        if (!force_local) {
                /*
                 * If the current CPU base is online, then the timer is