Home
last modified time | relevance | path

Searched hist:"8 c3b5e6e" (Results 1 – 3 of 3) sorted by relevance

/openbmc/linux/kernel/time/
H A Dtick-internal.h8c3b5e6e Tue Jul 13 08:39:48 CDT 2021 Thomas Gleixner <tglx@linutronix.de> hrtimer: Ensure timerfd notification for HIGHRES=n

If high resolution timers are disabled the timerfd notification about a
clock was set event is not happening for all cases which use
clock_was_set_delayed() because that's a NOP for HIGHRES=n, which is wrong.

Make clock_was_set_delayed() unconditially available to fix that.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20210713135158.196661266@linutronix.de
H A Dhrtimer.c8c3b5e6e Tue Jul 13 08:39:48 CDT 2021 Thomas Gleixner <tglx@linutronix.de> hrtimer: Ensure timerfd notification for HIGHRES=n

If high resolution timers are disabled the timerfd notification about a
clock was set event is not happening for all cases which use
clock_was_set_delayed() because that's a NOP for HIGHRES=n, which is wrong.

Make clock_was_set_delayed() unconditially available to fix that.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20210713135158.196661266@linutronix.de
/openbmc/linux/include/linux/
H A Dhrtimer.h8c3b5e6e Tue Jul 13 08:39:48 CDT 2021 Thomas Gleixner <tglx@linutronix.de> hrtimer: Ensure timerfd notification for HIGHRES=n

If high resolution timers are disabled the timerfd notification about a
clock was set event is not happening for all cases which use
clock_was_set_delayed() because that's a NOP for HIGHRES=n, which is wrong.

Make clock_was_set_delayed() unconditially available to fix that.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20210713135158.196661266@linutronix.de