drm_mock_sch..._duration_us(9)

💅 drm_mock_sch..._duration_us(9)

okay so first things first, bestie: this is a page from the Kernel API Manual, and it's all about one lil' function that tells the mock scheduler how long a job should take. yes, we're in ./drivers/gpu/drm/scheduler/tests territory — test-land, not production-land — so breathe, you're safe 💖

---

✨ NAME ✨

drm_mock_sched_job_set_duration_us — Set a job duration 🎀

---

🦋 SYNOPSIS 🦋

void drm_mock_sched_job_set_duration_us (struct drm_mock_sched_job *job
, unsigned int duration_us );

---

🌸 ARGUMENTS 🌸

• job — the job you're setting the duration for, like handing your bestie a little timer 🫶
• duration_us — the duration, in micro seconds. yes, micro. tiny. baby units. ⏱️

---

💜 DESCRIPTION 💜

okay so here's the tea ☕: jobs that have a duration set on them get automatically completed by the mock scheduler as the timeline progresses. no cap, it just happens for you.

BUT — and this is the plot twist 😭 — if a job without a set duration gets encountered in the timeline, then the auto-magic stops and you'll need to call drm_mock_sched_advance to bump the timeline forward yourself. so like, set the duration or be prepared to do the manual labour, iykyk 💅

lowkey important: the automatic completion is conditional on nothing in the way being duration-less. one vibe-ruiner job and it's manual mode for ya 🔥

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/scheduler/tests/sched_tests.h

• struct drm_mock_scheduler(9)
• struct drm_mock_sched_entity(9)
• struct drm_mock_sched_job(9)
• drm_mock_sched_job_submit(9)
• drm_mock_sched_job_is_finished(9)
• drm_mock_sched_job_wait_finished(9)
• drm_mock_sched_job_wait_scheduled(9)

like literally the whole mock scheduler friend group, go say hi 👑✨

---

and that's the whole page, bestie 💖 this iconic piece of documentation lives in ./drivers/gpu/drm/scheduler/tests, dated October 2026, and it's filed under drm_mock_sch..._duration_us(9). slay, go set some durations 🎀💅