Skip to content

Commit

Permalink
timekeeping: Distangle resume and clock-was-set events
Browse files Browse the repository at this point in the history
Resuming timekeeping is a clock-was-set event and uses the clock-was-set
notification mechanism. This is in the way of making the clock-was-set
update for hrtimers selective so unnecessary IPIs are avoided when a CPU
base does not have timers queued which are affected by the clock setting.

Distangle it by invoking hrtimer_resume() on each unfreezing CPU and invoke
the new timerfd_resume() function from timekeeping_resume() which is the
only place where this is needed.

Rename hrtimer_resume() to hrtimer_resume_local() to reflect the change.

With this the clock_was_set*() functions are not longer required to IPI all
CPUs unconditionally and can get some smarts to avoid them.

Signed-off-by: Thomas Gleixner <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Alexander Winkowski <[email protected]>
  • Loading branch information
KAGA-KOKO authored and dereference23 committed Jun 18, 2023
1 parent edd8efc commit 8949e57
Show file tree
Hide file tree
Showing 5 changed files with 16 additions and 9 deletions.
1 change: 0 additions & 1 deletion include/linux/hrtimer.h
Original file line number Diff line number Diff line change
Expand Up @@ -368,7 +368,6 @@ extern void timerfd_resume(void);
static inline void timerfd_clock_was_set(void) { }
static inline void timerfd_resume(void) { }
#endif
extern void hrtimers_resume(void);

DECLARE_PER_CPU(struct tick_device, tick_cpu_device);

Expand Down
11 changes: 4 additions & 7 deletions kernel/time/hrtimer.c
Original file line number Diff line number Diff line change
Expand Up @@ -919,20 +919,17 @@ void clock_was_set(void)
}

/*
* During resume we might have to reprogram the high resolution timer
* interrupt on all online CPUs. However, all other CPUs will be
* stopped with IRQs interrupts disabled so the clock_was_set() call
* must be deferred.
* Called during resume either directly from via timekeeping_resume()
* or in the case of s2idle from tick_unfreeze() to ensure that the
* hrtimers are up to date.
*/
void hrtimers_resume(void)
void hrtimers_resume_local(void)
{
WARN_ONCE(!irqs_disabled(),
KERN_INFO "hrtimers_resume() called with IRQs enabled!");

/* Retrigger on the local CPU */
retrigger_next_event(NULL);
/* And schedule a retrigger for all others */
clock_was_set_delayed();
}

/*
Expand Down
7 changes: 7 additions & 0 deletions kernel/time/tick-common.c
Original file line number Diff line number Diff line change
Expand Up @@ -439,6 +439,13 @@ void tick_resume_local(void)
else
tick_resume_oneshot();
}

/*
* Ensure that hrtimers are up to date and the clockevents device
* is reprogrammed correctly when high resolution timers are
* enabled.
*/
hrtimers_resume_local();
}

/**
Expand Down
2 changes: 2 additions & 0 deletions kernel/time/tick-internal.h
Original file line number Diff line number Diff line change
Expand Up @@ -162,3 +162,5 @@ DECLARE_PER_CPU(struct hrtimer_cpu_base, hrtimer_bases);

extern u64 get_next_timer_interrupt(unsigned long basej, u64 basem);
void timer_clear_idle(void);

void hrtimers_resume_local(void);
4 changes: 3 additions & 1 deletion kernel/time/timekeeping.c
Original file line number Diff line number Diff line change
Expand Up @@ -1687,8 +1687,10 @@ void timekeeping_resume(void)

touch_softlockup_watchdog();

/* Resume the clockevent device(s) and hrtimers */
tick_resume();
hrtimers_resume();
/* Notify timerfd as resume is equivalent to clock_was_set() */
timerfd_resume();
}

int timekeeping_suspend(void)
Expand Down

0 comments on commit 8949e57

Please sign in to comment.