cppc_get_perf(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cppc_get_perf(9) β€” like, the Kernel API Manual page you actually wanna read

okay so bestie, welcome to cppc_get_perf(9) from the Kernel API Manual ✨ this is the little function that goes and grabs a CPU's performance controls for you, and I'm gonna walk you through it like we're texting at 2am 🫢


πŸŽ€ NAME πŸŽ€

cppc_get_perf β€” literally just get a CPU's performance controls. that's the whole vibe. πŸ’«


🌸 SYNOPSIS 🌸

int cppc_get_perf (int cpu , struct cppc_perf_ctrls *perf_ctrls );

yes queen, that's the exact signature, don't @ me πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • cpu β€” the CPU whose performance controls you're trying to get πŸ‘‘ like, which one do you want, bestie? pick one.
  • perf_ctrls β€” a ptr to cppc_perf_ctrls. see cppc_acpi.h for the deets πŸ“„ iykyk.

✨ DESCRIPTION ✨

so here's the tea πŸ“ Desired Performance is not read β€” it's just returned as 0. that's it. that's the whole description. no cap, that's literally the fact. πŸ’€


πŸ”₯ RETURN πŸ”₯

  • 0 for success, with perf_ctrls filled in πŸŽ‰ slay.
  • -ERRNO otherwise 😭 (that's the error case, obviously).

πŸ’œ SEE ALSO πŸ’œ

the whole friend group, honestly 🌈 β€” and the kernel file ./drivers/acpi/cppc_acpi.c is the main character here:

go read them, bestie, they're iconic πŸ’…


ngl if you're here for the desired-perf value, it's 0. that's not a bug, that's the documented behaviour. periodt. πŸŽ€

okay that's the whole page!! mwah πŸ’– this came from the ./drivers/acpi source tree, dated October 2026, and it's cppc_get_perf(9) β€” go forth and get those performance controls, queen πŸ‘‘βœ¨

πŸ“¦ where this page comes from