vmw_cmd_bind_gb_surface(9)

okay so welcome to the manual for vmw_cmd_bind_gb_surface(9) — yep, that's the manual name, and this is the Kernel API Manual page for it. It's giving very specific kernel-command validation energy, and we're gonna read it together. 💅✨

💖 NAME 💖

vmw_cmd_bind_gb_surface — Validate SVGA_3D_CMD_BIND_GB_SURFACE command. That's the name, that's the job, and it's lowkey iconic. 🦋

✨ SYNOPSIS ✨

here's the signature, copied exactly because we do not mess with C types in this house:

int vmw_cmd_bind_gb_surface (struct vmw_private *dev_priv , struct
       vmw_sw_context *sw_context , SVGA3dCmdHeader *header );

🎀 ARGUMENTS 🎀

three arguments, three little icons — let's do a vibe check on each:

• dev_priv — Pointer to a device private struct. That's the device-private pointer, bestie. 🫶
• sw_context — The software context being used for this batch. Main character energy for the batch, fr fr. 🌸
• header — Pointer to the command header in the command stream. The header pointer, right where the command stream lives. 👑

🌈 SEE ALSO 🌈

okay so this is the crossover episode. The kernel file is ./drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c, and here's the full squad of linked references — every single one, no skipping:

• Kernel file ./drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c
• struct vmw_relocation(9)
• enum vmw_resource_relocation_type(9)
• struct vmw_resource_relocation(9)
• struct vmw_ctx_validation_info(9)
• struct vmw_cmd_entry(9)
• vmw_ptr_diff(9)
• vmw_execbuf_bindings_commit(9)
• vmw_bind_dx_query_mob(9)
• vmw_cmd_ctx_first_setup(9)
• vmw_execbuf_res_size(9)
• vmw_execbuf_rcache_update(9)
• vmw_execbuf_res_val_add(9)
• vmw_view_res_val_add(9)
• vmw_view_id_val_add(9)
• vmw_resource_context_res_add(9)
• vmw_resource_relocation_add(9)
• vmw_resource_relocations_free(9)
• vmw_resource_relocations_apply(9)
• vmw_resources_reserve(9)
• vmw_cmd_res_check(9)
• vmw_rebind_all_dx_query(9)
• vmw_rebind_contexts(9)
• vmw_view_bindings_add(9)
• vmw_cmd_cid_check(9)
• vmw_execbuf_info_from_res(9)
• vmw_query_bo_switch_prepare(9)
• vmw_query_bo_switch_commit(9)
• vmw_translate_mob_ptr(9)
• vmw_translate_guest_ptr(9)
• vmw_cmd_dx_define_query(9)
• vmw_cmd_dx_bind_query(9)
• vmw_cmd_begin_gb_query(9)
• vmw_cmd_begin_query(9)
• vmw_cmd_end_gb_query(9)
• vmw_cmd_end_query(9)
• vmw_cmd_wait_gb_query(9)
• vmw_cmd_wait_query(9)
• vmw_cmd_res_switch_backup(9)
• vmw_cmd_switch_backup(9)
• vmw_cmd_update_gb_image(9)
• vmw_cmd_update_gb_surface(9)
• vmw_cmd_readback_gb_image(9)
• vmw_cmd_readback_gb_surface(9)
• vmw_cmd_invalidate_gb_image(9)
• vmw_cmd_invalidate_gb_surface(9)
• vmw_cmd_shader_define(9)
• vmw_cmd_shader_destroy(9)
• vmw_cmd_set_shader(9)
• vmw_cmd_set_shader_const(9)
• vmw_cmd_bind_gb_shader(9)
• vmw_cmd_dx_set_single_constant_buffer(9)
• vmw_cmd_dx_set_constant_buffer_offset(9)
• vmw_cmd_dx_set_shader_res(9)
• vmw_cmd_dx_set_shader(9)
• vmw_cmd_dx_set_vertex_buffers(9)
• vmw_cmd_dx_set_index_buffer(9)
• vmw_cmd_dx_set_rendertargets(9)
• vmw_cmd_dx_clear_rendertarget_view(9)
• vmw_cmd_dx_clear_depthstencil_view(9)
• vmw_cmd_dx_set_so_targets(9)
• vmw_cmd_dx_check_subresource(9)
• vmw_cmd_dx_view_remove(9)
• vmw_cmd_dx_define_shader(9)
• vmw_cmd_dx_destroy_shader(9)
• vmw_cmd_dx_bind_shader(9)
• vmw_cmd_dx_genmips(9)
• vmw_cmd_dx_transfer_from_buffer(9)
• vmw_cmd_intra_surface_copy(9)
• vmw_execbuf_copy_fence_user(9)
• vmw_execbuf_submit_fifo(9)
• vmw_execbuf_submit_cmdbuf(9)
• vmw_execbuf_cmdbuf(9)
• vmw_execbuf_unpin_panic(9)
• __vmw_execbuf_release_pinned_bo(9)
• vmw_execbuf_release_pinned_bo(9)

before you go, bestie: the source/version footer says ./drivers/gpu/drm/vmwgfx, the date is October 2026, and the manual is vmw_cmd_bind_gb_surface(9). mwah 💋 periodt.