radeon_vce_get_create_msg(9)

💅 radeon_vce_get_create_msg — generate a VCE create msg

okay bestie, so this one is from the Kernel API Manual (kernel land, very main character energy) and it's literally about generating a VCE create msg. That's it. That's the whole vibe. Let's get into it 🎀

---

✨ SYNOPSIS ✨

int radeon_vce_get_create_msg (struct radeon_device *rdev , int ring ,
uint32_t handle , struct radeon_fence **fence );

like, it returns an int, and it takes four things. no cap, that's the whole signature. 🦋

---

🌸 ARGUMENTS 🌸

• rdev — the radeon_device pointer, aka your little handle on the whole radeon device situation 💖
• ring — the ring we should submit the msg to, iykyk 🌀
• handle — the VCE session handle to use, so the driver knows whose session this is 🔑
• fence — an optional fence to return. optional, bestie, so you can absolutely pass nothing if that's your mood ✨

---

💅 DESCRIPTION 💅

Open up a stream for HW test. That's it. That's the assignment. Go off, open that stream, do the HW test, slay 🔥

---

👑 SEE ALSO 👑

the kernel file lives at ./drivers/gpu/drm/radeon/radeon_vce.c and honestly the whole friend group is here, say hi to everybody:

• radeon_vce_init(9)
• radeon_vce_fini(9)
• radeon_vce_suspend(9)
• radeon_vce_resume(9)
• radeon_vce_idle_work_handler(9)
• radeon_vce_note_usage(9)
• radeon_vce_free_handles(9)
• radeon_vce_get_destroy_msg(9)
• radeon_vce_cs_reloc(9)
• radeon_vce_validate_handle(9)
• radeon_vce_cs_parse(9)
• radeon_vce_semaphore_emit(9)
• radeon_vce_ib_execute(9)
• radeon_vce_fence_emit(9)
• radeon_vce_ring_test(9)
• radeon_vce_ib_test(9)

---

💀 quick reminder: fence is the only optional one here, so don't be out here skipping rdev, ring or handle and then acting surprised. periodt.

---

okay that's the page!! 🫶 this little gem comes out of ./drivers/gpu/drm/radeon and it's dated October 2026 — so yes, it's giving future icon, and the manual name it lives under is radeon_vce_get_create_msg(9) in the Kernel API Manual. mwah, go open some streams 🍓💜