tmigr_cpu_deactivate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

tmigr_cpu_deactivate β€” puts the current CPU into inactive state, bestie. This page is from the Kernel API Manual, and it’s giving β€œsmall function, very specific job” energy πŸ’….

✨ SYNOPSIS ✨

u64 tmigr_cpu_deactivate (u64 nextexp );

πŸŽ€ ARGUMENTS πŸŽ€

  • nextexp β€” the next global timer expiry of the current CPU. That’s the value you’re passing in, okay? πŸŽ€

🌸 DESCRIPTION 🌸

Okay so real talk: this function must be called with interrupts disabled. Not β€œtry your best,” not β€œif you feel like it” β€” interrupts disabled, periodt. ⚠️

πŸ¦‹ RETURN πŸ¦‹

The return value is the next event expiry of the current CPU. But wait, there’s a plot twist 🫒: if this CPU is the top level migrator, or if the hierarchy is completely idle, then you get the next event expiry from the hierarchy instead. That’s it, that’s the return vibe ✨.

🌈 SEE ALSO 🌈

Peep the kernel file ./kernel/time/timer_migration.c and these iconic friends πŸ‘‘:


Byeeee from the ./kernel/time source corner, dated October 2026, on the tmigr_cpu_deactivate(9) page β€” slay and stay interrupt-safe πŸ’–πŸ¦‹πŸ«Ά

πŸ“¦ where this page comes from