get_next_timer_interrupt(9)

get_next_timer_interrupt(9) 🌸

okay bestie, welcome to the get_next_timer_interrupt(9) page from the Kernel API Manual. this is the kernel-time vibe check where we ask: what’s the next timer’s clock mono time? no cap. ✨

💖 NAME 💖

get_next_timer_interrupt — return the time (clock mono) of the next timer. periodt. 🕰️

🎀 SYNOPSIS 🎀

u64 get_next_timer_interrupt (unsigned long basej , u64 basem );

🦋 ARGUMENTS 🦋

• basej — base time jiffies, fr fr.
• basem — base time clock monotonic. that’s the monotonic baseline, iykyk.

✨ DESCRIPTION ✨

okay so this function returns the tick aligned clock monotonic time of the next pending timer, or KTIME_MAX if no timer is pending. iconic. 👑

and here are the little caveats, because of course there are caveats:

• If timer of global base was queued into timer migration hierarchy, the first global timer is not taken into account. 🙈
• If it was the last CPU of timer migration hierarchy going idle, the first global event is taken into account. 🫶

🔥 SEE ALSO 🔥

these are the related lore links, and yes there are a lot of them — collect them all, bestie:

• Kernel file ./kernel/time/timer.c, struct timer_base(9)
• __round_jiffies_relative(9)
• round_jiffies(9)
• round_jiffies_relative(9)
• __round_jiffies_up_relative(9)
• round_jiffies_up(9)
• round_jiffies_up_relative(9)
• timer_init_key(9)
• mod_timer_pending(9)
• mod_timer(9)
• timer_reduce(9)
• add_timer(9)
• add_timer_local(9)
• add_timer_global(9)
• add_timer_on(9)
• __timer_delete(9)
• timer_delete(9)
• timer_shutdown(9)
• __try_to_del_timer_sync(9)
• timer_delete_sync_try(9)
• __timer_delete_sync(9)
• timer_delete_sync(9)
• timer_shutdown_sync(9)
• fetch_next_timer_interrupt_remote(9)
• timer_unlock_remote_bases(9)
• timer_lock_remote_bases(9)
• timer_base_is_idle(9)
• timer_expire_remote(9)
• timer_base_try_to_set_idle(9)
• timer_clear_idle(9)
• __run_timers(9)

shoutout to the source/version ./kernel/time and the date October 2026 for this footer moment. mwah 💋✨