tick_nohz_idle_exit(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… tick_nohz_idle_exit

okay so bestie, welcome to the Kernel API Manual β€” this is tick_nohz_idle_exit(9) and honestly she's that girl who shows up right when the idle task dips out and gets the tick situation sorted. πŸŽ€ Let's get into it.


✨ NAME ✨

tick_nohz_idle_exit β€” update the tick upon idle task exit πŸ¦‹

✨ SYNOPSIS ✨

void tick_nohz_idle_exit (void );

✨ ARGUMENTS ✨

  • void β€” no arguments, bestie. none. zero. she takes nothing and gives everything πŸ’…

✨ DESCRIPTION ✨

so when the idle task exits, the tick gets updated depending on which of these situations we're in πŸ‘‘ like it's genuinely a vibe check for the tick:

  1. If the CPU is not in nohz_full mode (aka the most cases, the normie path), then restart the tick. periodt. πŸ”₯
  2. If the CPU is in nohz_full mode (the corner case, the main character scenario πŸ™ˆ):

2.1) If the tick can be kept stopped (no tick dependencies at all, like none), then re-evaluate the next tick and try to keep it stopped as long as possible. lowkey iconic β€” keep that tick asleep 😴✨

2.2) If the tick has dependencies though, restart the tick. no cap, it's gotta come back. πŸ’€

ngl, the whole point here is: figure out the tick's situation, then either restart it or keep it stopped as long as you possibly can. slay. 🌸

✨ SEE ALSO ✨

these are literally the whole friend group, go read them too πŸ§šπŸ’œ


so yeah, that's the page!! it lives in ./kernel/time and this version is dated October 2026 β€” mwah, love that for us πŸ’–β­ go forth and let your ticks be unbothered πŸ¦‹πŸŒˆ

πŸ“¦ where this page comes from