vmw_query_bo_switch_prepare(9)
π NAME π
hey bestie!! welcome to vmw_query_bo_switch_prepare(9) from the Kernel API Manual π«Ά
vmw_query_bo_switch_prepare β prepare to switch pinned buffer for queries.
β¨ SYNOPSIS β¨
it's giving this exact signature, no edits:
int vmw_query_bo_switch_prepare (struct vmw_private *dev_priv , struct
vmw_bo *new_query_bo , struct vmw_sw_context *sw_context );
π ARGUMENTS π
dev_privβ the device private structure.new_query_boβ the new buffer holding query results.sw_contextβ the software context used for this command submission.
π¦ DESCRIPTION π¦
okay so picture this: vmw_query_bo_switch_prepare does a vibe check on new_query_bo β is it suitable for holding query results? π it also checks if another buffer currently is pinned for query results. if so, it gets the state of sw_context ready for switching pinned buffers after the current command batch has been submitted successfully. that's the tea β β it's literally the prep era for the pinned-buffer switch π
π SEE ALSO π
the see-also squad is all here, bestie:
- 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_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_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)
mwah!! this page's source/version is ./drivers/gpu/drm/vmwgfx, and the date is October 2026 β see you in the kernel, bestie π«Άπ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms