cpuidle_coupled_set_waiting(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cpuidle_coupled_set_waiting(9)

okay so bestie, welcome to the Kernel API Manual ✨ β€” yes, that's the manual section, and yes, this page is about one very specific little function that lives in the cpuidle coupled-state universe πŸŒ€. Pull up a chair, grab a strawberry πŸ“, and let's get into it.


🌸 NAME 🌸

cpuidle_coupled_set_waiting β€” mark this cpu as in the wait loop πŸŽ€

Like, it literally just flags "hey, this cpu is waiting now" and that's the whole vibe check πŸ’….


πŸ¦‹ SYNOPSIS πŸ¦‹

int cpuidle_coupled_set_waiting (int cpu , struct cpuidle_coupled
*coupled , int next_state );

Copy it exactly, bestie β€” no cap, it's giving function signature realness 😌.


✨ ARGUMENTS ✨

  • cpu β€” the target cpu 🎯 (this is the one you're marking, iykyk)
  • coupled β€” the struct coupled that contains the current cpu πŸ‘‘
  • next_state β€” the index in drv->states of the requested state for this cpu πŸ”₯

πŸ’– DESCRIPTION πŸ’–

So here's the tea β˜•: it updates the requested idle state for the specified cpuidle device. That's it, that's the whole thing πŸ’«.

And then β€” plot twist β€” it returns the number of waiting cpus πŸ”’. Literally returns a count, no cap πŸ™ˆ.


🌈 SEE ALSO 🌈

Kernel file ./drivers/cpuidle/coupled.c β€” and like, the whole coupled cpuidle cinematic universe πŸ’€:


okay that's the whole page, bestie β€” you ate that 🫢. this one came out of ./drivers/cpuidle and it's dated October 2026 ⭐, and we're signing off with the biggest cpuidle_coupled_set_waiting(9) energy ever πŸ’œπŸ’…πŸ§š

πŸ“¦ where this page comes from