vmw_dx_shader_scrub(9)
π
vmw_dx_shader_scrub(9) β the Kernel API Manual, but make it cute π
π NAME π
vmw_dx_shader_scrub β the function that gets the device to unbind a MOB from a DX shader, bestie.
β¨ SYNOPSIS β¨
int vmw_dx_shader_scrub (struct vmw_resource *res );
πΈ ARGUMENTS πΈ
resβ the shader resource. Thatβs the one, the only, the resource in question. π«Ά
π¦ DESCRIPTION π¦
Okay so real talk: this function unbinds a MOB from the DX shader without requiring the MOB dma_buffer to be reserved first. No cap, thatβs the whole little magic trick. β¨
But the plot twist is that the driver still considers the MOB bound. Yep, still on the books. So even after this scrub situation, itβs not like the driver is pretending the MOB was never bound.
Then later, once the driver eventually decides to unbind the MOB, it doesnβt need to access the context. Thatβs it, thatβs the vibe. π¦
π SEE ALSO π
Kernel file: ./drivers/gpu/drm/vmwgfx/vmwgfx_shader.c
vmw_res_to_dx_shader(9)vmw_dx_shader_commit_notify(9)vmw_dx_shader_unscrub(9)vmw_dx_shader_create(9)vmw_dx_shader_bind(9)vmw_dx_shader_unbind(9)vmw_dx_shader_cotable_list_scrub(9)vmw_dx_shader_res_free(9)vmw_dx_shader_add(9)vmw_shader_id_ok(9)vmw_shader_key(9)vmw_shader_remove(9)vmw_compat_shader_add(9)vmw_shader_lookup(9)
This page is serving source/version + date realness from ./drivers/gpu/drm/vmwgfx, dated October 2026, and the page tag is literally vmw_dx_shader_scrub(9). Slay, bye πβ¨
π¦ 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