scx_softlockup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… scx_softlockup(9) πŸ’…

Okay bestie, welcome to the Kernel API Manual page for scx_softlockup β€” the sched_ext softlockup handler. This is highkey emergency-scheduler content, so hydrate and pay attention. πŸ’–


πŸŽ€ NAME πŸŽ€

scx_softlockup β€” sched_ext softlockup handler. That’s the whole vibe of the name section, periodt. ✨

✨ SYNOPSIS ✨

void scx_softlockup (u32 dur_s );

🌸 ARGUMENTS 🌸

  • dur_s β€” the number of seconds of CPU stuck due to soft lockup. Basically the stuck-o-meter reading, ngl. πŸ•°οΈ

πŸ¦‹ DESCRIPTION πŸ¦‹

On some multi-socket setups (e.g. 2x Intel 8480c), the BPF scheduler can live-lock the system by making many CPUs target the same DSQ to the point where soft-lockup detection triggers. Not me learning that many CPUs can all pile onto the same DSQ and just… create chaos. 😭

This function is called from the soft-lockup watchdog when the triggering point is close, and it tries to unjam the system and abort the BPF scheduler. It’s literally the β€œbestie, we need to get out of this situation” function. πŸ”₯

πŸ’œ SEE ALSO πŸ’œ

The kernel file is ./kernel/sched/ext/ext.c β€” that’s the home base 🏠 β€” and here’s the full friend group, no cap:

Signed, sealed, delivered by ./kernel/sched/ext β€” October 2026 β€” scx_softlockup(9) πŸ’Œ

πŸ“¦ where this page comes from