drm_mock_sch...ait_finished(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_mock_sch...ait_finished(9) β€” the glam edition

Okay so bestie, we're in the Kernel API Manual, section 9 (that's the kernel internals one, iykyk), and the page header is stylin' as drm_mock_sch...ait_finished(9) β€” yes it's truncated with ellipsis, no I didn't do that, that's just the vibe the page came with. πŸŽ€


✨ NAME ✨

drm_mock_sched_job_wait_finished β€” literally just waits until a job is finished. That's it. That's the whole personality. ⏳


✨ SYNOPSIS ✨

bool drm_mock_sched_job_wait_finished (struct drm_mock_sched_job *job ,
       long timeout );

She returns a bool, she takes two things, and she's not complicated about it. 🫢


✨ ARGUMENTS ✨

  • job β€” the job you're waiting for. The main character of this lil operation. πŸ‘‘
  • timeout β€” how long you're willing to wait, measured in jiffies. Not seconds, not vibes β€” jiffies. Don't come crying to me when your math is off. 😭

✨ RETURN ✨

Returns true if it's finished within the timeout you provided. Otherwise? false. That's the entire tea. πŸ“

No cap β€” if it times out, you get false, not an error, not a tantrum, just false. Plan accordingly bestie.

✨ SEE ALSO ✨

Lowkey the whole friend group is linked here, so let's go:

All of these are literally in ./drivers/gpu/drm/scheduler/tests if you wanna snoop. πŸ”₯


And that's the page, bestie β€” brought to you by ./drivers/gpu/drm/scheduler/tests, dated October 2026, filed under drm_mock_sch...ait_finished(9). Slay, go read the source, ily, bye πŸ’–πŸŒΈπŸ§š

πŸ“¦ where this page comes from