tmigr_isolat...lude_cpumask(9)

💅 tmigr_isolated_exclude_cpumask — ngl the manual page bestie

okay so real talk, this is the kernel API manual page for tmigr_isolated_exclude_cpumask(9) and yes the title is a whole mouthful, we're getting through it together 🫶

---

✨ NAME ✨

tmigr_isolated_exclude_cpumask — literally just Exclude given CPUs from hierarchy. that's the whole vibe. no cap. 🔥

---

🎀 SYNOPSIS 🎀

int tmigr_isolated_exclude_cpumask (struct cpumask *exclude_cpumask );

that's it. one function, one argument, returns an int. iconic behaviour honestly 🌸

---

🦋 ARGUMENTS 🦋

• exclude_cpumask — the cpumask to be excluded from the timer migration hierarchy. like, this is the list of CPUs that are getting left out of the party 💀

---

💖 DESCRIPTION 💖

so here's the tea. this function can be called from cpuset code to hand over the new set of isolated CPUs that should be excluded from the hierarchy. main character energy for real 👑

and like, important detail: online CPUs that are not present in exclude_cpumask but were already excluded are brought back to the hierarchy. so it's not just a one-way exclusion situation — some CPUs are literally getting invited back in. the way that works is so slay 🧚

heads up bestie — the functions to isolate/unisolate need to be called locally and they can sleep. so don't be calling them from somewhere spicy. 😭

---

🌈 SEE ALSO 🌈

• Kernel file ./kernel/time/timer_migration.c ⭐
• struct tmigr_walk(9)
• tmigr_cpu_activate(9)
• tmigr_handle_remote(9)
• tmigr_requires_handle_remote(9)
• tmigr_cpu_new_timer(9)
• tmigr_cpu_deactivate(9)
• tmigr_quick_check(9)

go read those next, iykyk 💅

---

and that's the whole page bestie, no notes 🙈 this came from the <pink>./kernel/time</pink> section, dated October 2026, and the manual name is tmigr_isolat...lude_cpumask(9) in case you forgot already (i almost did 😭). periodt. 💜