STRUCT VMW_RESOURCE(9)

💅 struct vmw_resource 💅

okay so bestie, we're in the Kernel API Manual and this page is literally struct vmw_resource(9) — the base class for hardware resources. no cap, it's the blueprint for hardware resource vibes. let's get into it ✨

🌸 NAME 🌸

struct vmw_resource — base class for hardware resources 🫶

✨ SYNOPSIS ✨

here's the whole struct, copied exactly because we do not mess with the source, periodt:

       struct vmw_resource {
           struct kref kref;
           struct vmw_private *dev_priv;
           int id;
           u32 used_prio;
           unsigned long guest_memory_size;
           u32 res_dirty : 1;
           u32 guest_memory_dirty : 1;
           u32 coherent : 1;
           struct vmw_bo *guest_memory_bo;
           unsigned long guest_memory_offset;
           unsigned long pin_count;
           const struct vmw_res_func *func;
           struct rb_node mob_node;
           struct list_head lru_head;
           struct list_head binding_head;
           struct vmw_resource_dirty *dirty;
           void (*res_free) (struct vmw_resource *res);
           void (*hw_destroy) (struct vmw_resource *res);
        };

🎀 Members 🎀

• kref — For refcounting. 🧚
• dev_priv — Pointer to the device private for this resource. Immutable.
• id — Device id. Protected by dev_priv::resource_lock.
• used_prio — Priority for this resource. ⭐
• guest_memory_size — Guest memory buffer size. Immutable.
• res_dirty — Resource contains data not yet in the guest memory buffer. Protected by resource reserved.
• guest_memory_dirty — Guest memory buffer contains data not yet in the HW resource. Protected by resource reserved.
• coherent — Emulate coherency by tracking vm accesses. 🦋
• guest_memory_bo — The guest memory buffer if any. Protected by resource reserved.
• guest_memory_offset — Offset into the guest memory buffer if any. Protected by resource reserved. Note that only a few resource types can have a guest_memory_offset different from zero. 🙈
• pin_count — The pin count for this resource. A pinned resource has a pin-count greater than zero. It is not on the resource LRU lists and its guest memory buffer is pinned. Hence it can't be evicted. 🔥
• func — Method vtable for this resource. Immutable.
• mob_node — Node for the MOB guest memory rbtree. Protected by guest_memory_bo reserved.
• lru_head — List head for the LRU list. Protected by dev_priv::resource_lock.
• binding_head — List head for the context binding list. Protected by the dev_priv::binding_mutex
• dirty — resource's dirty tracker 🫶
• res_free — The resource destructor.
• hw_destroy — Callback to destroy the resource on the device, as part of resource destruction. 💀

🌈 SEE ALSO 🌈

the kernel file is ./drivers/gpu/drm/vmwgfx/vmwgfx_drv.h — and here's the whole cross-ref squad, iykyk:

• struct vmw_surface_metadata(9)
• struct vmw_surface(9)
• struct vmw_res_cache_entry(9)
• enum vmw_dma_map_mode(9)
• struct vmw_sg_table(9)
• struct vmw_piter(9)
• struct vmw_sw_context(9)
• enum vmw_sm_type(9)
• has_sm4_context(9)
• has_sm4_1_context(9)
• has_sm5_context(9)
• has_gl43_context(9)
• vmw_resource_mob_attached(9)
• vmw_fifo_caps(9)
• vmw_is_cursor_bypass3_enabled(9)
• vmw_piter_next(9)
• vmw_piter_dma_addr(9)
• vmw_piter_page(9)
• struct vmw_diff_cpy(9)
• VMW_DEBUG_USER(9)
• VMW_DEBUG_KMS(9)
• vmw_fifo_mem_read(9)
• vmw_fifo_mem_write(9)

💖 that's a wrap, bestie! source: ./drivers/gpu/drm/vmwgfx • date: October 2026 • page: struct vmw_resource(9) 🫶