drm_gem_vram_create(9)

📦 version 7.3.1, in nixpkgs unstable

💖 drm_gem_vram_create(9) 💖

okay so bestie, welcome to the kernel API manual — this is drm_gem_vram_create(9) and it is literally the glow-up moment for your VRAM-backed GEM object ✨

🌸 NAME 🌸

drm_gem_vram_create — Creates a VRAM-backed GEM object

no cap, that's the whole vibe: it makes you a GEM object that lives in VRAM 💅

✨ SYNOPSIS ✨

struct drm_gem_vram_object * drm_gem_vram_create (struct drm_device *dev
, size_t size , unsigned long pg_align );

look at that signature, she's iconic 🫶

🎀 ARGUMENTS 🎀

  • dev — the DRM device, like, the whole reason we're here 💖
  • size — the buffer size in bytes (yes, bytes, we're being precise)
  • pg_align — the buffer's alignment, measured in multiples of the page size 🧚

🦋 DESCRIPTION 🦋

so here's the tea ☕ — GEM objects get allocated by calling struct drm_driver.gem_create_object, if it's set. if it's not set? then kzalloc will be used instead. that's the fallback, bestie, and it slays in a pinch.

drivers can totally set their own GEM object functions in struct drm_driver.gem_create_object. and if no functions are set at all, then the new GEM object will use the default functions from GEM VRAM helpers. default queen behavior 👑

🔥 RETURN 🔥

a new instance of struct drm_gem_vram_object on success — yay 🎉 — or an ERR_PTR-encoded error code otherwise 😭

fr fr, always check that return value. if it's an ERR_PTR-encoded error code, that's not a cute moment, that's a bug in your code.

🌈 SEE ALSO 🌈

like, go read all of them, iykyk 💀📚

mwah, that's the page! 🫶 this one was brought to you by ./drivers/gpu/drm, stamped October 2026 — stay hydrated, check your error pointers, and slay your VRAM allocations, bestie 💜🎀

📦 where this page comes from