radeon_vce_get_destroy_msg(9)

📦 version 7.3.1, in nixpkgs unstable

💅 radeon_vce_get_destroy_msg 💅

okay so this is a page from the Kernel API Manual, bestie — it's radeon_vce_get_destroy_msg(9), and literally all it does is generate a VCE destroy msg. that's it. that's the whole vibe. but like, in a kernel-y way, so let's get into it 🎀

✨ NAME ✨

radeon_vce_get_destroy_msg — generate a VCE destroy msg 🦋

🌸 SYNOPSIS 🌸

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

like, copy that exactly, no cap, don't rearrange the args, the compiler will absolutely come for you 🙈

💖 ARGUMENTS 💖

  • rdev — a radeon_device pointer. that's your whole radeon device, the main character of this story 👑
  • ring — the ring we should submit the msg to. yes, we — you and this function, bestie, working together 🫶
  • handle — the VCE session handle to use. it's the one you got handed earlier, don't lose it 💀
  • fence — optional fence to return. optional!! so you can pass nothing and it's fine, lowkey freeing ✨

🔥 DESCRIPTION 🔥

so what does it actually do on this fine October 2026 day?

it closes up a stream — either for a HW test, or because userspace failed to do it itself 😭 (yes, that second one happens, and yes, this function is the cleanup crew showing up with a mop and a cute little attitude 💅).

it's giving "somebody has to close this stream and apparently it's me" energy, and honestly? iconic. periodt. 🌈

🎀 SEE ALSO 🎀

okay this is the part where the whole squad gets introduced, so let's go, all of these live in the kernel file ./drivers/gpu/drm/radeon/radeon_vce.c and you can look up any of them:

ngl bestie, if a stream is left open, this is the one that closes it — so like, respect it 💖

alright that's the page!! it lives under ./drivers/gpu/drm/radeon, it's dated October 2026, and it's filed in the manual as radeon_vce_get_destroy_msg(9) — mwah, slay, go close some streams 🧚⭐🍓

📦 where this page comes from