Re: [PATCH] hrtimer: Update softirq_expires_next correctly after __hrtimer_get_next_event()
From: Lorenzo Colitti
Date: Tue Apr 20 2021 - 04:15:19 EST
On Fri, Apr 16, 2021 at 1:47 AM Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:
> Enable tracing and enable the following tracepoints:
> [...]
Sorry for the delay. I had to learn a bit about how to use the tracing
infrastructure. I don't know if I can post here, but to my untrained
eye, one big difference between the old (fast) code and the new (slow)
code is that the new code calls tick_program_event() much more. It
looks like that makes most of the difference.
With the old code, hrtimer_start_range_ns almost never calls
tick_program_event at all, but the new code seems to call it twice on
every timer update.