scx_process_sync_ecaps(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… scx_process_sync_ecaps(9) πŸ’…

okay bestie, welcome to the Kernel API Manual entry for scx_process_sync_ecaps β€” yes the title repeats up there, that's just how manpages are, it's giving tradition ✨


🌸 NAME 🌸

scx_process_sync_ecaps β€” sync this cpu's ecaps to pshard->caps[] 🫢


✨ SYNOPSIS ✨

void scx_process_sync_ecaps (struct rq *rq , struct task_struct *prev );

literally the whole signature, no cap πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • rq β€” the cid's cpu rq πŸ‘‘
  • prev β€” rq's previous task from the in-progress dispatch πŸ¦‹

πŸ’– DESCRIPTION πŸ’–

so here's the tea, bestie: pshard->caps[] is the target configuration. meanwhile pcpu->ecaps is the effective transposed copy β€” it's owned by the cid's cpu and it gets written only here, under rq's lock. one writer, one lock, no drama 🌈

and then there's this: a sched that newly gains baseline access here is owed an update_idle so it learns the cid's idle state. periodt. such a gain arms the per-rq SCX_RQ_SUB_IDLE_RENOTIFY gate so the next idle pick delivers it πŸ”₯ so yeah, it's a whole little chain, iykyk.


πŸ¦‹ SEE ALSO πŸ¦‹


πŸ’€ that's the whole list, don't skip it, these all matter fr fr

and that's a wrap, bestie 🧚 this page lives in ./kernel/sched/ext and it's dated October 2026 β€” mwah, go read some kernel source πŸ’œπŸŽ€β­

πŸ“¦ where this page comes from