idle_inject_set_duration(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… idle_inject_set_duration(9) β€” the Kernel API Manual, bestie edition πŸŽ€

okay so this is idle_inject_set_duration, straight out of the kernel API manual, and she's a little helper for updating the idle duration and run duration on an idle injection device. yes that's a lot of words. we'll get through it together 🫢


✨ NAME ✨

idle_inject_set_duration β€” the idle-and-run-duration update helper, no cap ✨


🌸 SYNOPSIS 🌸

void idle_inject_set_duration (struct idle_inject_device *ii_dev ,
unsigned int run_duration_us , unsigned int idle_duration_us );

she takes three things and returns nothing (void, iconic, doesn't need to report back πŸ’…). note the literal spacing in there, we're copying it exactly, character for character, fr fr.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • ii_dev β€” the idle injection control device structure. this is your main character, the thing you're tweaking πŸ’–
  • run_duration_us β€” the CPU run time to allow, measured in microseconds. so like, how long the CPU gets to actually cook πŸ”₯
  • idle_duration_us β€” the CPU idle time to inject, also in microseconds. this is the forced lil nap 😴
lowkey the easiest way to remember it: run first, idle second. microseconds for both. don't mix them up ngl 🫢

🌈 SEE ALSO 🌈

like, the whole friend group 🧚 go read idle_inject_get_duration(9) if you want the read-only bestie version, and idle_inject_set_latency(9) if latency is more your vibe πŸ’œ


that's the whole page bestie, she's short and sweet πŸ“ β€” brought to you from ./drivers/powercap, dated October 2026, in the Kernel API Manual, filed under idle_inject_set_duration(9). slay, go set some durations πŸ’…βœ¨

πŸ“¦ where this page comes from