tick_resume_local(9)

💅 tick_resume_local(9)

okay so welcome to the Kernel API Manual, bestie — this is the glow-up page for tick_resume_local, and honestly it's a short one but it slaps. pull up a chair 🎀

---

✨ NAME ✨

tick_resume_local — wakes the local tick device back up, no cap ⏰💖

---

🌸 SYNOPSIS 🌸

void tick_resume_local (void );

that's the whole vibe. no args, no drama, just a void going in and a void coming out 🫶

---

🦋 ARGUMENTS 🦋

• void — literally no arguments. nothing to pass, nothing to worry about. it's giving unbothered 💅

---

⭐ DESCRIPTION ⭐

so here's the tea: you call this from the local CPU when you're doing an unfreeze, or when the XEN resume magic happens. that's it, that's the whole job 🔥

and the best part? no locks required, bestie. not a single one. why? because nothing can change the per cpu device — it's all yours on that CPU, so there's zero need to guard it. iconic behaviour honestly 👑

ngl this one's short but the details still ate — local CPU only, unfreeze + XEN resume, no locking. that's the entire lore 📖✨

---

🌈 SEE ALSO 🌈

• the kernel file ./kernel/time/tick-common.c — go read it, iykyk 📂
• tick_is_oneshot_available(9)
• tick_broadcast_oneshot_control(9)
• tick_suspend_local(9)
• tick_suspend(9)
• tick_resume(9)
• tick_freeze(9)
• tick_unfreeze(9)
• tick_init(9)

the whole tick friend group, fr fr 🧚‍♀️💜

---

and that's a wrap, bestie!! 🍓 this page lives in ./kernel/time and it's dated October 2026 — so yes, your fave is from the future 😭💀 mwah, go resume some ticks 💖👑