cppc_get_highest_perf(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ cppc_get_highest_perf β€” a Kernel API Manual moment ✨

okay so bestie, welcome to the Kernel API Manual entry for cppc_get_highest_perf(9) and honestly? she's a little icon. tiny function, big main character energy πŸ’…


🌸 NAME 🌸

cppc_get_highest_perf β€” get the highest performance register value πŸ’– (yes, that's literally her whole job and she does it flawlessly, no cap)


πŸ¦‹ SYNOPSIS πŸ¦‹

int cppc_get_highest_perf (int cpunum , u64 *highest_perf );

πŸŽ€ ARGUMENTS πŸŽ€

  • cpunum β€” the CPU you're pulling the highest performance from πŸ‘‘ like, which one bestie, be specific
  • highest_perf β€” the return address 🫢 this is where the answer gets dropped off, so pls make sure it's a real place

⭐ RETURN ⭐

  • 0 β€” success slay ✨ everything went off without a hitch
  • -EIO β€” otherwise 😭 like if it's not 0, it's this, and that's the whole story

πŸ’œ SEE ALSO πŸ’œ

the whole friend group, fr fr β€” kernel file ./drivers/acpi/cppc_acpi.c plus:

acpi_get_psd_map(9), cpc_ffh_supported(9), cpc_supported_by_cpu(9), pcc_data_alloc(9), acpi_cppc_processor_probe(9), acpi_cppc_processor_exit(9), cpc_read_ffh(9), cpc_read_ffh_fb_ctrs(9), cpc_write_ffh(9), cppc_get_desired_perf(9), cppc_get_nominal_perf(9), cppc_get_epp_perf(9), cppc_get_perf_caps(9), cppc_perf_ctrs_in_pcc_cpu(9), cppc_perf_ctrs_in_pcc(9), cppc_get_perf_ctrs(9), cppc_set_epp(9), cppc_get_auto_act_window(9), cppc_set_auto_act_window(9), cppc_get_auto_sel(9), cppc_set_auto_sel(9), cppc_set_enable(9), cppc_get_perf(9), cppc_set_perf(9), cppc_get_perf_limited(9), cppc_set_perf_limited(9), cppc_get_transition_latency(9)


πŸ’€ quick vibe check: that's a lot of siblings and every single one of them is invited to the function call. don't skip any, iykyk πŸ™ˆ

🌈 and that's the page!! brought to you by the fine folks in ./drivers/acpi, dated October 2026 β€” go forth and read those registers bestie, ily, bye!! πŸŽ€πŸ’–βœ¨

πŸ“¦ where this page comes from