DRM_IOCTL_GEM_CHANGE_HANDLE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… DRM_IOCTL_GEM_CHANGE_HANDLE(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” yes, the whole manual, and yes, we're gonna get through it together 🫢 this one's short and sweet, so grab your iced coffee and let's go ✨


🌸 NAME 🌸

DRM_IOCTL_GEM_CHANGE_HANDLE β€” move an object to a different handle. that's it. that's the whole vibe. a lil glow-up for your handle πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

DRM_IOCTL_GEM_CHANGE_HANDLE

like, that's literally it. iconic minimalism. no args in the synopsis, no drama, just the name πŸ”₯


πŸŽ€ DESCRIPTION πŸŽ€

so some applications β€” and the manpage is calling out CRIU specifically, notable queen behavior πŸ‘‘ β€” need their objects to have specific gem handles. like, they're not flexible about it. they need the exact handle, no substitutions, no "close enough," no cap πŸ’―

and that's what this ioctl does: it changes the object at one gem handle to use a new gem handle. one handle in, that same object now answers to a different handle. a rebrand, if you will ✨

that's the entire description, bestie. short, sweet, ate and left no crumbs πŸ“


πŸ’– SEE ALSO πŸ’–

the deep lore 🌈 β€” go read these if you want the full picture:

like, that's a lot of links, but that's the list, so we're listing them all. we don't skip. skipping is not the vibe πŸ™ˆ


reminder babe: this page has no options section, no return values, no errors listed. don't go looking for them, they're not here. what you see is what you get πŸ’€

and that's the whole page, bestie!! 🌟 you understood it, you slayed it, you're literally the main character of the kernel docs now πŸ‘‘

sign-off time πŸŽ€ this one came from ./tools/perf/trace/beauty/incl... (yes the footer path is literally truncated with an ellipsis, that's how it shipped, we don't fix πŸ’€) and it's dated October 2026 β€” so go forth, change those handles, and stan DRM_IOCTL_GEM_CHANGE_HANDLE fr fr πŸ’œπŸ¦‹βœ¨

πŸ“¦ where this page comes from