vmw_kms_help...ation_finish(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ vmw_kms_helper_validation_finish(9) ✨

okay bestie, welcome to the Kernel API Manual πŸ’… this is vmw_kms_help...ation_finish(9) and yes the title is literally truncated like that in the header, we don't make the rules, we just slay within them πŸŽ€


🌸 NAME 🌸

vmw_kms_helper_validation_finish β€” the helper that handles the post KMS command submission cleanup and the fencing 🧚 no cap, that's the whole job description


πŸ¦‹ SYNOPSIS πŸ¦‹

void vmw_kms_helper_validation_finish (struct vmw_private *dev_priv ,
struct drm_file *file_priv , struct vmw_validation_context *ctx , struct
vmw_fence_obj **out_fence , struct drm_vmw_fence_rep __user *
user_fence_rep );

literally five arguments, returns void, iconic πŸ™ˆ


πŸ’– ARGUMENTS πŸ’–

  • dev_priv β€” pointer to the device-private struct. it's giving "everything you need to know about this device lives here" πŸ‘‘
  • file_priv β€” pointer that identifies the client, and it's the one that matters when user-space fencing is being used 🫢
  • ctx β€” pointer to the validation context. the whole cleanup-and-fence vibe check happens around this bad boy ✨
  • out_fence β€” if it's non-NULL, you get a refcounted fence pointer handed back to you. if it's NULL, well… you get nothing, and that's on you πŸ’€
  • user_fence_rep β€” if it's non-NULL, this is a pointer to a user-space address area where the user-space fence info gets copied. if it's NULL, no copy happens, simple as 🌸

πŸ‘‘ SEE ALSO πŸ‘‘

the Kernel file lives right here, go read it fr fr:

./drivers/gpu/drm/vmwgfx/vmwgfx_kms.c

and here's the whole friend group, every single one of them, no skipping 🫢:

vmw_du_plane_unpin_surf(9), vmw_du_plane_cleanup_fb(9), vmw_du_primary_plane_atomic_check(9), vmw_du_crtc_duplicate_state(9), vmw_du_crtc_reset(9), vmw_du_crtc_destroy_state(9), vmw_du_plane_duplicate_state(9), vmw_du_plane_reset(9), vmw_du_plane_destroy_state(9), vmw_du_connector_duplicate_state(9), vmw_du_connector_reset(9), vmw_du_connector_destroy_state(9), vmw_kms_readback(9), vmw_kms_srf_ok(9), vmw_kms_new_framebuffer(9), vmw_kms_check_display_memory(9), vmw_crtc_state_and_lock(9), vmw_kms_check_implicit(9), vmw_kms_check_topology(9), vmw_kms_atomic_check_modeset(9), vmw_du_update_layout(9), vmw_guess_mode_timing(9), vmw_kms_update_layout_ioctl(9), vmw_kms_helper_dirty(9), vmw_kms_create_implicit_placement_property(9), vmw_kms_suspend(9), vmw_kms_resume(9), vmw_kms_lost_device(9), vmw_du_helper_plane_update(9), vmw_connector_mode_valid(9), vmw_connector_get_modes(9)


and that's the page bestie πŸŽ€ sign-off time: this one comes from the source ./drivers/gpu/drm/vmwgfx, dated October 2026, and it's vmw_kms_help...ation_finish(9) all over again at the bottom because manpages love a symmetry moment πŸ’– go fence something responsibly πŸ¦‹

πŸ“¦ where this page comes from