PROBE::SCHEDULER.M(3stap)

✨ NAME ✨

probe::scheduler.migrate — bestie, this is the probe that catches a task migrating across cpus 💅

Like, the exact moment a process packs its little bags and moves from one CPU to another. Iconic behaviour, honestly.

---

🦋 SYNOPSIS 🦋

probe scheduler.migrate {}

That's it. That's the whole vibe. No arguments, no fuss, just the probe point sitting there ready to fire. 🎀

---

🌸 VALUES 🌸

Every one of these is handed to you when the probe fires. Collect them all like they're stickers:

• priority — the priority of the task that's doing the migrating.
• task — the process that is being migrated. The main character of this whole operation, fr fr.
• cpu_to — the destination cpu. Where the task is headed. 🛬
• pid — PID of the task being migrated. Gotta know who is travelling.
• name — name of the probe point. (Yes, it's the probe's own name — it's giving self-aware ✨)
• cpu_from — the original cpu. Where the task just left from. 🛫

ngl, cpu_from and cpu_to together are lowkey the whole plot. Task leaves one, arrives at the other. A journey. A glow-up. 💖

---

👑 SEE ALSO 👑

• tapset::scheduler(3stap) — go read this one next, it's the friend group this probe belongs to 🫶

---

Okay so that's the whole page, and it ate, no crumbs. This was pulled straight from the SystemTap Tapset Reference, version Ver (yeah, that's literally what the footer said, I'm not making it up 😭), dated September 2026. Slay, go probe something. 💜🌈⭐