cppc_perf_ctrs_in_pcc(9)

📦 version 7.3.1, in nixpkgs unstable

💅 cppc_perf_ctrs_in_pcc(9) — from the Kernel API Manual, bestie

Okay so picture this: you're deep in the kernel docs, section 9, and you land on cppc_perf_ctrs_in_pcc. Sounds scary? It's not. It's literally a vibe check for performance counters, and I'm gonna walk you through it 🫶

✨ NAME ✨

cppc_perf_ctrs_in_pcc — check if any perf counters are in a PCC region. That's it, that's the whole job. No cap 💖

🌸 SYNOPSIS 🌸

bool cppc_perf_ctrs_in_pcc (void );

Yes bestie, it returns a bool. Yes, she takes nothing. Iconic minimalism 👑

🎀 ARGUMENTS 🎀

  • void — no arguments. Zero. None. She doesn't want your parameters, she doesn't need your parameters, she's booked and busy being a void 💅

💖 DESCRIPTION 💖

So here's the tea 🍓 CPPC is super flexible about how CPU performance counters get accessed — like, there are options, it's giving choose-your-own-adventure. One of those choices is PCC regions, and the thing about PCC regions is they can have a high access latency 😭 like, not fast. Not snappy. We're waiting.

That's exactly why this routine exists: it lets callers of cppc_get_perf_ctrs find out about that latency ahead of time, so nobody gets jump-scared by a slow read. It's the "hey bestie, just so you know before you commit" of kernel APIs 🙈✨

🔥 RETURN 🔥

  • true — if any of the counters are in PCC regions 👀
  • false — otherwise ✌️

🦋 SEE ALSO 🦋

Kernel file ./drivers/acpi/cppc_acpi.c — and honestly, the whole friend group:

ngl the whole list is a mood, go read them, iykyk 🌈

And that's the page!! Signing off from ./drivers/acpi, dated October 2026 — this section 9 page (cppc_perf_ctrs_in_pcc(9)) ate and left no crumbs. Periodt 💀💜🧚

📦 where this page comes from