vmw_event_fe...action_queue(9)

💅 vmw_event_fence_action_queue(9) — Kernel API Manual, bestie ✨

Okay so the page header shows the shortened vmw_event_fe...action_queue(9) thing, and the manual name is Kernel API Manual. The full function name in the synopsis is vmw_event_fence_action_queue — iconic. 🎀

🌸 NAME 🌸

vmw_event_fence_action_queue — Post an event for sending when a fence object seqno has passed. ✨

🦋 SYNOPSIS 🦋

int vmw_event_fence_action_queue (struct drm_file *file_priv , struct vmw_fence_obj *fence , struct drm_pending_event *event , uint32_t *tv_sec , uint32_t *tv_usec , bool interruptible );

🎀 ARGUMENTS 🎀

• file_priv — the file connection on which the event should be posted. 💖
• fence — the fence object on which to post the event. 🦋
• event — the event to be posted. This event should’ve been alloced using k[mz]alloc, and it should’ve been completely initialized. 🫶
• tv_sec — if non-null, the variable pointed to will be assigned current time tv_sec val when the fence signals. ⭐
• tv_usec — must be set if tv_sec is set, and the variable pointed to will be assigned the current time tv_usec val when the fence signals. 🌈
• interruptible — interruptible waits if possible. 💜

💖 DESCRIPTION 💖

😭 As a side effect, the object pointed to by event may have been freed when this function returns. If this function returns with an error code, the caller needs to free that object.

Like, fr fr read that part twice, bestie. 🫶

🦋 SEE ALSO 🦋

• Kernel file ./drivers/gpu/drm/vmwgfx/vmwgfx_fence.c
• struct vmw_event_fence_action(9)
• vmw_fence_obj_lookup(9)
• vmw_event_fence_action_seq_passed(9)

That’s a wrap, bestie 💜 This page’s source spot is ./drivers/gpu/drm/vmwgfx, the date is October 2026, and the page tag is vmw_event_fe...action_queue(9). Bye fr fr 🫶✨