drm_sched_wqueue_start(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ drm_sched_wqueue_start(9) β€” start scheduler submission ✨

Okay bestie, welcome to the drm_sched_wqueue_start page from the Kernel API Manual πŸ’– this one is short and sweet and honestly kind of a glow-up moment for your scheduler, so let's get into it.


🌸 NAME 🌸

drm_sched_wqueue_start β€” start scheduler submission πŸ‘‘

πŸ¦‹ SYNOPSIS πŸ¦‹

void drm_sched_wqueue_start (struct drm_gpu_scheduler *sched );

πŸŽ€ ARGUMENTS πŸŽ€

  • sched β€” the scheduler instance, aka the main character of this whole function 🫢

πŸ’… DESCRIPTION πŸ’…

So here's the tea: this function restarts the scheduler after drm_sched_wqueue_stop has stopped it. That's it, that's the vibe β€” you stopped it, now you're bringing it back. Iconic behavior honestly πŸ’€βœ¨

But listen, and this is the important part: this function is not necessary for 'conventional' startup. Nope, not even a little. Because the scheduler is already fully operational after drm_sched_init succeeded. So if you're out here calling this during a normal init flow, bestie… you don't need to 😭 it's giving extra.

Fr fr: only reach for this when you're un-stopping a scheduler that drm_sched_wqueue_stop put on pause. Conventional startup already ate with drm_sched_init. πŸ‘‘

🌈 SEE ALSO 🌈

Everything else in the scheduler cinematic universe, all linked up and thriving:


And that's the whole page, bestie β€” short, sweet, and to the point πŸ“ This one lives in ./drivers/gpu/drm/scheduler, dated October 2026, and it's brought to you straight from the Kernel API Manual. Go forth and start that wqueue πŸ’œπŸ§šβœ¨

πŸ“¦ where this page comes from