cpuidle_state_is_coupled(9)

📦 version 7.3.1, in nixpkgs unstable

💤 cpuidle_state_is_coupled(9) 💤

okay so bestie, welcome to the Kernel API Manual — yes this is a section 9 situation, we're in kernel-doc territory, put your hair up, we're getting technical ✨

🌸 NAME 🌸

cpuidle_state_is_coupled — check if a state is part of a coupled set

like, is this idle state running solo or is it in a situationship with other cpus? that's the whole vibe check 💅

🦋 SYNOPSIS 🦋

bool cpuidle_state_is_coupled (struct cpuidle_driver *drv , int state );

it returns a bool, she's simple, she's clean, she tells you yes or no and doesn't elaborate 😌

🎀 ARGUMENTS 🎀

  • drv — the struct cpuidle_driver for the platform. it's giving "main character energy" for your whole platform's idle story 👑
  • state — the index of the target state in drv->states. literally just the little number that points at which state we're asking about 🍓

💖 DESCRIPTION 💖

Returns true if the target state is coupled with cpus besides this one.

that's it. that's the whole function. no cap, no extra lore, no hidden side quests. if the state is coupled with other cpus → true. if not → not true. iconic behaviour honestly 🫶

🌈 SEE ALSO 🌈

the whole coupled crew, in order, no one left out because we do not do that here 💜

ngl if you're deep in the coupled cpuidle lore you should probably read all of these, they're a set, they come as a package deal 😭

and that's the page!! tysm for reading, this has been cpuidle_state_is_coupled(9) from the ./drivers/cpuidle girlies, dated October 2026 — mwah, drink water, go touch grass, and may your idle states never deadlock 💅✨🦋

📦 where this page comes from