drm_mock_sched_entity_new(9)
π drm_mock_sched_entity_new
okay so bestie, this is a page from the Kernel API Manual for drm_mock_sched_entity_new β yes it's a mouthful, yes we're gonna get through it together π«Ά
β¨ NAME β¨
drm_mock_sched_entity_new β literally just creates a new mock scheduler entity. that's the whole gig. no cap π
πΈ SYNOPSIS πΈ
struct drm_mock_sched_entity * drm_mock_sched_entity_new (struct kunit
*test , enum drm_sched_priority priority , struct drm_mock_scheduler
*sched );
like, it hands you back a pointer to a struct drm_mock_sched_entity * and takes three things. we'll go through them one by one, don't worry π
π¦ ARGUMENTS π¦
testβ the KUnit test that owns the entity. yes, it's the main character here, the entity belongs to it πpriorityβ the scheduling priority. anenum drm_sched_priority, so pick your vibe βschedβ the mock scheduler on which the entity can be scheduled. think of it as the venue where the entity gets to perform π
π« RETURN π«
a brand new mock scheduler entity, with its allocation managed by the test. so the test handles the cleanup β the entity doesn't just wander off on its own, it's got a whole management situation going on π
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/scheduler/tests/mock_scheduler.cβ that's where the magic lives, go read it iykyk drm_mock_sched_entity_free(9)drm_mock_sched_job_new(9)drm_mock_sched_new(9)drm_mock_sched_fini(9)drm_mock_sched_advance(9)
fr fr, those SEE ALSO entries are your besties too β the _free one especially, since your test is managing that allocation. don't leave it hanging π
okay that's the whole page! source and version check: this one's from ./drivers/gpu/drm/scheduler/tests, dated October 2026, and it's part of the Kernel API Manual for drm_mock_sched_entity_new(9). slay, you're done here π§π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms