ENUM DRM_GEM_OBJECT_STATUS(9)

✨ enum drm_gem_object_status(9) ✨

okay so hiiii, welcome to the Kernel API Manual, bestie 🫶 this page is all about enum drm_gem_object_status(9), and it's basically a little bitmask of object state for fdinfo reporting. iconic behavior only, no cap. 💅

🌸 NAME 🌸

enum drm_gem_object_status — bitmask of object state for fdinfo reporting. periodt. ✨

🌈 SYNOPSIS 🌈

enum drm_gem_object_status {
    DRM_GEM_OBJECT_RESIDENT ,
    DRM_GEM_OBJECT_PURGEABLE ,
    DRM_GEM_OBJECT_ACTIVE

};

🧸 Constants 🧸

• DRM_GEM_OBJECT_RESIDENT — object is resident in memory (ie. not unpinned). 💖
• DRM_GEM_OBJECT_PURGEABLE — object marked as purgeable by userspace. 🫧
• DRM_GEM_OBJECT_ACTIVE — object is currently used by an active submission. 🔥

💖 Description 💖

so this is the bitmask of status used for fdinfo memory stats — peek at drm_gem_object_funcs.status and drm_show_fdinfo if you want the full receipts. 👑

here's the tea: an object can report DRM_GEM_OBJECT_PURGEABLE and still be active or not resident, and in that case drm_show_fdinfo will not account for it as purgeable. so drivers do not need to check whether the buffer is idle and resident before returning this bit — meaning userspace can mark a buffer as purgeable even while it is still busy on the GPU. it will not get reported in the puregeable stats until it becomes idle. the status gem object func does not need to consider this. periodt. 💀✨

🔗 SEE ALSO 🔗

• Kernel file: ./include/drm/drm_gem.h
• struct drm_gem_object_funcs(9)
• struct drm_gem_lru(9)
• struct drm_gem_object(9)
• DRM_GEM_FOPS(9)
• DEFINE_DRM_GEM_FOPS(9)
• drm_gem_get_huge_mnt(9)
• drm_gem_object_get(9)
• drm_gem_object_put(9)
• drm_gem_object_is_shared_for_memory_stats(9)
• drm_gem_is_imported(9)
• drm_gem_gpuva_init(9)
• drm_gem_for_each_gpuvm_bo(9)
• drm_gem_for_each_gpuvm_bo_safe(9)

this cutie comes from source ./include/drm, dated October 2026, and it's the enum drm_gem_object_status(9) page — byeeeeee 🎀🦋💖