sched_set_itmt_core_prio(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, you're looking at the Kernel API Manual page for sched_set_itmt_core_prio(9) β€” yes, the whole name, and yes, it's giving kernel-core realness πŸ’…βœ¨

🌸 NAME 🌸

sched_set_itmt_core_prio β€” Set CPU priority based on ITMT πŸ’–

✨ SYNOPSIS ✨

void sched_set_itmt_core_prio (int prio , int cpu );

that's the whole vibe: prio first, then cpu, no cap πŸŽ€

πŸŽ€ ARGUMENTS πŸŽ€

  • prio β€” Priority of cpu πŸ’– like, the priority level you're handing over, bestie.
  • cpu β€” The CPU number πŸŽ€ the actual CPU ID getting that priority.

πŸ’… DESCRIPTION πŸ’…

okay so the pstate driver is the main character here: it will find out the max boost frequency and call this function to set a priority proportional to the max boost frequency. CPUs with higher boost frequency will receive higher priority β€” literally "higher boost, higher priority" energy πŸ”₯ no cap.

and the best part? no need to rebuild sched domain after updating the CPU priorities. the sched domains have no dependency on CPU priorities, so they're literally unbothered 🫢✨

the way that sched domains have zero dependency on CPU priorities and need zero rebuild is so iconic, fr fr πŸ’…

πŸ¦‹ SEE ALSO πŸ¦‹


this page lives in ./arch/x86/kernel, dated October 2026, and it's the sched_set_itmt_core_prio(9) version β€” slay, bestie, bye! πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from