scx_bpf_kick_cid(9)

📦 version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to scx_bpf_kick_cid(9) from the Kernel API Manual ✨ this one is literally here to trigger a reschedule on the CPU mapped to @cid, and it's giving scheduler main-character energy 💅.

🎀 NAME 🎀

scx_bpf_kick_cid — trigger reschedule on the CPU mapped to @cid 🦋

✨ SYNOPSIS ✨

__bpf_kfunc void scx_bpf_kick_cid (s32 cid , u64 flags , const struct
       bpf_prog_aux *aux );

🌸 ARGUMENTS 🌸

  • cid — the cid to kick 💖
  • flags — the SCX_KICK_* flags, periodt.
  • aux — implicit BPF argument to access bpf_prog_aux hidden from BPF progs 🙈

💅 DESCRIPTION 💅

This is the cid-addressed equivalent of scx_bpf_kick_cpu, fr fr. An invalid cid aborts the scheduler via scx_cid_to_cpu — not cute, very real 😭.

Caps are enforced on the delivery path: a kick is dropped if the caller lacks baseline access on cid, and a SCX_KICK_PREEMPT degrades to a plain reschedule if the caller lacks SCX_CAP_PREEMPT for a task outside its subtree. That's the whole rulebook, bestie 🫶.

lowkey important: an invalid cid aborts the scheduler via scx_cid_to_cpu 💀 do not test this for fun.

🔮 SEE ALSO 🔮

not me dropping the entire SEE ALSO roster, because bestie we do not skip names 😤:

xoxo, source/version: ./kernel/sched/ext, dated October 2026 — mwah 💋✨

📦 where this page comes from