PROBE::SCHEDULER.K(3stap)

✨ PROBE::SCHEDULER.KTHREAD_STOP β€” the 3stap girlies know ✨

okay bestie, pull up a chair 🫢 this is a SystemTap tapset probe page, section 3stap, and it's about one very specific little moment in a kernel thread's life. no cap.


πŸ’– NAME πŸ’–

probe::scheduler.kthread_stop β€” a thread that was created by kthread_create is being stopped

like. it's the goodbye scene. the thread has served its purpose and the kernel is like "ok queen, that's a wrap" πŸ’…


🌸 SYNOPSIS 🌸

probe scheduler.kthread_stop {}

that's it. no arguments, no fuss, just vibes. you just write the probe and it fires. periodt.


πŸŽ€ VALUES πŸŽ€

these are the local variables you get to peek at inside the probe handler. it's giving backstage pass ✨

  • thread_priority β€” the priority of the thread. yes, its whole priority situation. iconic.
  • thread_pid β€” the PID of the thread that's being stopped. the little ID badge of the thread whose story is ending 😭
ngl, both of these are values β€” meaning they're available to you inside the probe body, not something you pass in. don't be out here trying to feed them to the probe. it takes nothing. zero. empty braces energy.

πŸ‘‘ SEE ALSO πŸ‘‘

  • tapset::scheduler(3stap) β€” go read the scheduler tapset page if you want the whole cinematic universe, not just this one scene 🌈

πŸ¦‹ a lil sign-off πŸ¦‹

this was brought to you by the SystemTap Tapset Reference, and the page is dated September 2026. yes bestie, the future. we're early. slay πŸ’œ

stay curious, read your manpages, and remember: every thread that stops is just a thread that ate and left no crumbs. πŸ”₯✨

πŸ“¦ where this page comes from