vmw_resource_mob_attached(9)

💖 vmw_resource_mob_attached(9) 💖

okay so bestie, this is the Kernel API Manual page for vmw_resource_mob_attached, and it's basically a tiny vibe check: does this resource currently have a mob attached, or not? That's the whole main-character question. 💅✨

🎀 NAME 🎀

• vmw_resource_mob_attached — whether a resource currently has a mob attached.

✨ SYNOPSIS ✨

bool vmw_resource_mob_attached (const struct vmw_resource *res );

🫶 ARGUMENTS 🫶

• res — The resource. Like, the actual resource you're asking about, bestie.

💀 RETURN 💀

true if the resource has a mob attached, false otherwise. That's it — no mysterious in-between era. 😭

🌈 SEE ALSO 🌈

okay so if you're going down the rabbit hole (and you know you are), peep these:

• Kernel file ./drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
• struct vmw_resource(9)
• 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_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)

bestie, that's the whole page. shoutout to source/version ./drivers/gpu/drm/vmwgfx, date October 2026, and the manual page vmw_resource_mob_attached(9). now go forth and check those mobs 💖✨🦋