PROBE::SCHEDULER.C(3stap)

💅 probe::scheduler.ctxswitch (3stap) 💅

okay bestie, gather round, because we are talking about probe::scheduler.ctxswitch from the Scheduler Tapset — it's giving 3stap, it's giving kernel drama, and honestly? iconic.

---

✨ NAME ✨

probe::scheduler.ctxswitch — a context switch is occuring. yes, fr fr, that's literally the whole vibe: the CPU is dumping one process and picking up another, and this probe is your front-row seat 🍿

---

🦋 SYNOPSIS 🦋

probe scheduler.ctxswitch {}

no args, no drama, just vibes 💅

---

🎀 VALUES 🎀

okay so when this probe fires, it hands you a whole little gift bag of variables. here's every single one, no gatekeeping 🫶

• next_pid — the PID of the process that's getting switched in (the one stepping up, main character energy 👑)
• name — the name of the probe point. yes babe, the probe point itself has a name, and this is it
• prev_pid — the PID of the process getting switched out (sorry babe, your scene is over 😭)
• prev_task_name — the name of the process that's getting switched out
• next_priority — the priority of the process being switched in
• nexttsk_state — the state of the process being switched in
• next_tid — the TID of the process being switched in
• prevtsk_state — the state of the process being switched out
• prev_tid — the TID of the process being switched out
• next_task_name — the name of the process being switched in
• prev_priority — the priority of the process being switched out

heads up bestie: yes, next_pid/next_tid and prev_pid/prev_tid are different things, and yes, nexttsk_state/prevtsk_state are spelled exactly like that with no underscore. do not try to "fix" them, I'm begging 🙈

---

🌸 SEE ALSO 🌸

• tapset::scheduler(3stap) — go read the whole tapset, it's the mothership ✨

---

and that's the whole page, periodt 💖 no notes, no cap, every value accounted for, vibe check passed.

SystemTap Tapset Reference, September 2026 edition — mwah, love u, go probe something 🔥🦋⭐