STRUCT DRM_VMW_FENCE_EVENT_ARG(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct drm_vmw_fence_event_arg(9) πŸ’…

okay so this one is from the Kernel API Manual (manual section 9, kernel API, iykyk), and it's literally just the struct page for struct drm_vmw_fence_event_arg β€” the args you hand over when you want a fence event. That's it, that's the whole vibe. Let's get into it ✨


🌸 NAME 🌸

struct drm_vmw_fence_event_arg β€”

...and that's genuinely it, bestie. The NAME line is literally just the struct name with a little dash and nothing after it. No summary, no tagline. She said "my name is enough." main character energy fr fr πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

       struct drm_vmw_fence_event_arg {
           __u64 fence_rep;
           __u64 user_data;
           __u32 handle;
           __u32 flags;
        };

look at her. four fields. clean. no skips. copy it exactly, don't be cute with it 🫢


πŸ¦‹ Members πŸ¦‹

  • fence_rep β€” a pointer to the fence_rep structure, cast to __u64 β€” or 0 if the fence isn't supposed to be referenced by user-space. That's the whole deal: cast-to-__u64 pointer, or a big fat zero. no in-between, no vibes 🌈
  • handle β€” attaches the event to this fence only. one fence, one handle, very exclusive, very "you're the only fence for me" πŸ’–
  • flags β€” a set of flags, as defined above. (the manpage says "as defined above" β€” so scroll up and go find them, bestie, that's where they live πŸ‘€)

and yes, user_data is sitting right there in the SYNOPSIS with no little member blurb of its own on this page. she's mysterious. she contains multitudes. we respect her privacy πŸ™ˆ


⭐ SEE ALSO ⭐

the whole friend group, no cap:

  • Kernel file ./include/uapi/drm/vmwgfx_drm.h

and the icons themselves:

  • enum drm_vmw_handle_type(9)
  • struct drm_vmw_getparam_arg(9)
  • struct drm_vmw_size(9)
  • union drm_vmw_surface_create_arg(9)
  • struct drm_vmw_fence_rep(9)
  • struct drm_vmw_bo_rep(9)
  • union drm_vmw_alloc_bo_arg(9)
  • struct drm_vmw_control_stream_arg(9)
  • struct drm_vmw_cursor_bypass_arg(9)
  • struct drm_vmw_fence_wait_arg(9)
  • struct drm_vmw_shader_create_arg(9)
  • struct drm_vmw_gb_surface_create_req(9)
  • struct drm_vmw_gb_surface_create_rep(9)
  • union drm_vmw_gb_surface_create_arg(9)
  • union drm_vmw_gb_surface_reference_arg(9)
  • enum drm_vmw_synccpu_op(9)
  • struct drm_vmw_synccpu_arg(9)
  • union drm_vmw_extended_context_arg(9)
  • struct drm_vmw_handle_close_arg(9)
  • struct drm_vmw_gb_surface_create_ext_req(9)
  • union drm_vmw_gb_surface_create_ext_arg(9)
  • union drm_vmw_gb_surface_reference_ext_arg(9)
  • struct drm_vmw_msg_arg(9)
  • struct drm_vmw_mksstat_add_arg(9)
  • struct drm_vmw_mksstat_remove_arg(9)

heads up bestie: flags tells you the flags are "as defined above," and the fence_rep field cares very much whether it's a real __u64-cast pointer or a literal 0. get those two right and you're golden πŸ’œ

and that's the page!! πŸ“ sourced from ./include/uapi/drm, dated October 2026, and yes the footer still says struct drm_v...ce_event_arg(9) because the title got truncated and nobody fixed it. iconic. slay. bye bestie πŸ§šβœ¨πŸ’–

πŸ“¦ where this page comes from