drm_mock_sched_advance(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_mock_sched_advance(9)

okay so bestie, this is a page straight out of the Kernel API Manual (the drm_mock_sched_advance(9) one, yes bestie we're being official today ✨), and honestly it's kind of a slay.


🌸 NAME 🌸

drm_mock_sched_advance β€” bestie, it Advances the mock scheduler timeline. that's the whole vibe. no cap. πŸ’…


✨ SYNOPSIS ✨

unsigned int drm_mock_sched_advance (struct drm_mock_scheduler *sched ,
unsigned int num );

like, you hand it a scheduler and a number and it just goes. iconic behaviour tbh πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • sched β€” the Scheduler timeline to advance. this is the main character of the whole operation πŸ‘‘
  • num β€” By how many jobs to advance. how far forward we're skipping, literally 🧚

πŸ’– DESCRIPTION πŸ’–

so here's the tea: Advancing the scheduler timeline by a number of seqnos will trigger signalling of the hardware fences and unlinking the jobs from the internal scheduler tracking.

read that again. seqnos go up β†’ hardware fences get signalled β†’ jobs get unlinked from the internal scheduler tracking. all in one lil advance. ate and left no crumbs πŸ”₯

and why would you want that? because this can be used from test cases which want complete control of the simulated job execution timing. complete control. the dream, fr fr.

for example (and this is the part that lives in my head rent free 😭): submitting one job with no set duration would never complete it before test cases advances the timeline by one.

⚠️ bestie, clock that: a job with no set duration just sits there until the test case moves the timeline by one. it does not complete itself. it has zero initiative. πŸ’€ so if your test is just staring at a job like "any day now…" β€” nope, you gotta advance the timeline yourself. you're the one driving. 🫢

🌈 SEE ALSO 🌈

the whole mock scheduler friend group, honestly β€” collect them all πŸ“


and that's a wrap, bestie πŸŽ€ this page lives in ./drivers/gpu/drm/scheduler/tests and it's dated October 2026 β€” yes, the future πŸ’œ mwah, go advance some timelines βœ¨πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from