vc4_cl_lookup_bos(9)

💅 vc4_cl_lookup_bos 💅

okay bestie, welcome to the Kernel API Manual entry for vc4_cl_lookup_bos — yes that's the whole title, and yes it's a lot of consonants, but we're gonna get through it together 🫶

---

🌸 NAME 🌸

vc4_cl_lookup_bos — sets up exec->bo[] with the GEM objects that the job references. literally that's her whole job, and she ate ✨

---

🎀 SYNOPSIS 🎀

int vc4_cl_lookup_bos (struct drm_device *dev , struct drm_file
*file_priv , struct vc4_exec_info *exec );

that's the whole signature, no cap. three pointers in, one int out 💫

---

🦋 ARGUMENTS 🦋

• dev — the DRM device. main character of the hardware world 💻
• file_priv — the DRM file for this fd. her personal file, iykyk 🗂️
• exec — the V3D job being set up. this is the one we're dressing up for the runways 👑

---

🔥 DESCRIPTION 🔥

so here's the vibe check: the command validator needs to reference BOs by their index within the submitted job's BO list. not by name, not by pointer, by index. periodt 💅

and that's exactly what this function does — it does the validation of the job's BO list, and it handles the reference counting for the lifetime of the job. so the whole time that job is alive, the refs are held down. iconic behavior, honestly 🎀

ngl the refcounting part is the important bit — she's holding the door open for those objects for as long as the job needs them 🔒

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/vc4/vc4_gem.c
• vc4_submit_cl_ioctl(9)

go read those next bestie, they're in the same friend group 🧚

---

and that's the page!! 🍓 this little love letter lives in ./drivers/gpu/drm/vc4, dated October 2026, from the Kernel API Manual — vc4_cl_lookup_bos(9) and out 💜⭐