arch_enable...pacity_scale(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ arch_enable_hybrid_capacity_scale(9) β€” the Kernel API Manual, bestie edition πŸ¦‹

Okay so we're in the Kernel API Manual today and the star of the show is arch_enable_hybrid_capacity_scale(9)</p> β€” yes the header line is literally truncated to arch_enable...pacity_scale(9) because apparently even the manpage title has main character energy and refuses to fit. Iconic. Anyway πŸ’…


✨ NAME ✨

arch_enable_hybrid_capacity_scale β€” Enable hybrid CPU capacity scaling 🧚

Like, that's it. That's the whole name. It enables hybrid CPU capacity scaling. Slay.


🌸 SYNOPSIS 🌸

bool arch_enable_hybrid_capacity_scale (void );

Note the return type, bestie: bool. It gives you a boolean. It's giving "yes or no, no in-between." πŸŽ€


πŸ’– ARGUMENTS πŸ’–

  • void β€” no arguments. Zero. Nada. Nothing. It takes nothing β€” she works alone, she's independent, and honestly? Respect. 🫢

πŸ”₯ DESCRIPTION πŸ”₯

So here's the tea β˜• β€” this function allocates memory for the per-CPU data that hybrid CPU capacity scaling uses, then it initializes that memory, and then it sets the static key that controls the code paths for all of it. Three steps. One function. She ate. πŸ’…βœ¨

⚠️ Real talk though: it must be called before arch_set_cpu_capacity. That's not a vibe suggestion, that's a rule. Do it out of order and, like… don't. 😭

πŸ‘‘ SEE ALSO πŸ‘‘

  • The kernel file ./arch/x86/kernel/cpu/aperfmperf.c β€” go read the source, iykyk πŸ¦‹
  • arch_set_cpu_capacity(9) β€” the one you gotta call after this one, remember? No cap. πŸ™ˆ

And that's the whole page, bestie! 🌈 This little gem lives in the Kernel API Manual, comes from the source path ./arch/x86/kernel/cpu, and the version/date stamp at the bottom says October 2026 β€” dated arch_enable...pacity_scale(9), obviously, because we're back to that truncated title again πŸ’€. Periodt. β­πŸ“

πŸ“¦ where this page comes from