vmw_cmd_dx_..._from_buffer(9)

okay so this is the Kernel API Manual page vmw_cmd_dx_..._from_buffer(9), and today’s main character is vmw_cmd_dx_transfer_from_buffer. 💖 we are validating the SVGA_3D_CMD_DX_TRANSFER_FROM_BUFFER command, and the vibes are immaculate.

🌸 NAME 🌸

vmw_cmd_dx_transfer_from_buffer — Validate SVGA_3D_CMD_DX_TRANSFER_FROM_BUFFER command.

✨ SYNOPSIS ✨

bestie, here is literally the signature, character for character:

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

🎀 ARGUMENTS 🎀

• dev_priv — Pointer to a device private struct. it’s giving “device private struct” energy, and we respect it.
• sw_context — The software context being used for this batch. software context main character behavior, honestly.
• header — Pointer to the command header in the command stream. the header is right there in the command stream, bestie.

🦋 SEE ALSO 🦋

first up, the kernel file:

• ./drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c

then the whole bestie roll call, all of it, no skipping:

• 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_bind_gb_surface(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_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)

mwah 💋 this page is from the ./drivers/gpu/drm/vmwgfx source/version line, dated October 2026, and it’s literally the vmw_cmd_dx_..._from_buffer(9) page. slay. 🫶