cppc_get_perf_limited(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cppc_get_perf_limited(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” yes that's the manual name, we're fancy now πŸŽ€ β€” and today's main character is cppc_get_perf_limited, which lowkey just reads a register for you. Let's get into it ✨


✨ SYNOPSIS ✨

int cppc_get_perf_limited (int cpu , u64 *perf_limited );

that's the whole vibe. two args, one int back. slay 🫢


🌸 ARGUMENTS 🌸

  • cpu β€” the CPU you're pulling the Performance Limited register from. like, which CPU. you gotta pick one, girl, we're not mind readers πŸ’…
  • perf_limited β€” a pointer where the Performance Limited value gets stashed. bring your own storage, we just fill it in πŸŽ€

πŸ¦‹ DESCRIPTION πŸ¦‹

so the value that comes back holds sticky status bits β€” and by sticky I mean they hang around, they don't just evaporate β€” and those bits are telling you about performance limitations imposed by the platform. that's the whole plot. no cap 🧚


πŸ”₯ RETURN πŸ”₯

  • 0 β€” success, we ate πŸ’–
  • -EIO β€” failure, it's giving pain 😭
  • -EOPNOTSUPP β€” not supported. she's just not available rn πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘

okay this list is long but every single one of these deserves their moment, periodt:

like… the whole friend group showed up πŸŒˆπŸ’œ


ngl bestie, if you get -EOPNOTSUPP it's genuinely not you, it's the platform πŸ’€

and that's the page!! sourced straight from ./drivers/acpi, dated October 2026 ⭐ mwah, ilysm, go read some registers πŸ’…πŸ’–

πŸ“¦ where this page comes from