drm_sched_rq_add_entity(9)

✨ drm_sched_rq_add_entity(9) ✨

okay so bestie, welcome to the Kernel API Manual entry for drm_sched_rq_add_entity(9) — literally the glow-up moment where a scheduler entity gets yeeted onto a run queue 💅 this one's short and sweet, no cap.

---

🌸 NAME 🌸

drm_sched_rq_add_entity — add an entity 🎀

---

🦋 SYNOPSIS 🦋

struct drm_gpu_scheduler * drm_sched_rq_add_entity (struct
       drm_sched_entity *entity , ktime_t ts );

like, it hands you back a struct drm_gpu_scheduler * — main character return type fr fr 👑

---

💖 ARGUMENTS 💖

• entity — the scheduler entity in question, the little star of the show 🌟
• ts — the submission timestamp, ktime_t flavored ⏱️ (yes it matters, don't skip it)

---

🔥 DESCRIPTION 🔥

Adds a scheduler entity to the run queue. that's it, that's the whole vibe ✨ it's giving "short function, big responsibility." obsessed actually 🫶

---

👑 RETURN 👑

Returns the DRM scheduler</> selected to handle this entity — OR NULL if the entity has been stopped and cannot be submitted to 😭 so like, always check for NULL bestie, the entity could be in its flop era and you'd never know 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/scheduler/sched_rq.c
• drm_sched_rq_init(9)
• drm_sched_rq_remove_entity(9)
• drm_sched_rq_pop_entity(9)
• drm_sched_rq_select_entity(9)

go read the whole squad, they're all iconic in their own way 🧚💜

---

reminder: NULL is a real possibility here, not a jump scare 🙈 handle it and you're slaying.

---

and that's the page!! source lives at ./drivers/gpu/drm/scheduler, version vibes are Kernel API Manual, and the date stamp is October 2026 — mwah, bye bestie, go add some entities 💅🍓⭐