cpuidle_coup...cpus_waiting(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’€ cpuidle_coup...cpus_waiting(9) πŸ’€

ok so this is a page from the Kernel API Manual and honestly? it's a little baddie. it's short, it's sweet, and it does exactly one job. let's get into it bestie 🫢


✨ NAME ✨

cpuidle_coupled_cpus_waiting β€” check if all cpus in a coupled set are waiting πŸ‘€

like, the entire vibe of this function is just "hey... are we all here? is everyone in the wait loop? no cap?" πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

bool cpuidle_coupled_cpus_waiting (struct cpuidle_coupled *coupled );

yes she returns a bool and yes that's iconic of her. true or false, no in-between, periodt. πŸ”₯


🌸 ARGUMENTS 🌸

  • coupled β€” the struct coupled that contains the current cpu. that's it. that's the whole argument. she's lowkey a one-argument girly and we respect it πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

Returns true if all cpus coupled to this target state are in the wait loop.

the way that's literally the whole description 😭 and honestly same β€” why be verbose when you can just be correct? so yeah: everyone coupled to this target state, chillin' in the wait loop? true. not everyone? false. main character energy is checking on your friends fr fr.


🌈 SEE ALSO 🌈

ok buckle up bestie this list is LONG and every single one of these is coming with us, no skipping 🧚

Kernel file ./drivers/cpuidle/coupled.c

the whole coupled squad ate, ngl. go read all of them, iykyk πŸ’€


πŸ’‘ friendly reminder: this function only tells you whether everyone's waiting β€” it doesn't make anyone wait. no extra lore, that's just what the manpage says 🫢

that's the page!! she's from ./drivers/cpuidle (yes, the kernel file lives there too) and she's dated October 2026 ✨ thanks for reading bestie, now go check your wait loops πŸ’œπŸ“

πŸ“¦ where this page comes from