vmw_user_bo_synccpu_grab(9)

✨ vmw_user_bo_synccpu_grab(9) ✨

okay bestie, welcome to the Kernel API Manual 💖 — today we're learning about vmw_user_bo_synccpu_grab, which is literally the function that grabs a struct vmw_bo for CPU access 🫶

🌸 NAME 🌸

vmw_user_bo_synccpu_grab — grab a struct vmw_bo for cpu access, idle previous GPU operations on the buffer, and optionally block it for further command submissions. no cap, that's the whole vibe check 🎀

🦋 SYNOPSIS 🦋

int vmw_user_bo_synccpu_grab (struct vmw_bo *vmw_bo , uint32_t flags );

💅 ARGUMENTS 💅

• vmw_bo — Pointer to the buffer object being grabbed for CPU access. this is the main character of the operation ✨
• flags — Flags indicating how the grab should be performed. iykyk, they change the whole energy of the grab 🌈

🔥 RETURN 🔥

Zero on success, negative error code on error. fr fr, that's it. but lowkey there are two specific ones you should know about 👑

• -EBUSY — returned if a dontblock operation is requested and the buffer object is busy 😭 like, it's occupied, come back later
• -ERESTARTSYS — returned if a wait is interrupted by a signal 💀 rude but valid

👑 DESCRIPTION 👑

A blocking grab will be automatically released when tfile is closed. literally so convenient, it cleans up after itself 🧚✨

💜 SEE ALSO 💜

Kernel file ./drivers/gpu/drm/vmwgfx/vmwgfx_bo.c, plus the whole friend group 🫶:

• vmw_bo_free(9)
• vmw_bo_pin_in_placement(9)
• vmw_bo_pin_in_vram_or_gmr(9)
• vmw_bo_pin_in_vram(9)
• vmw_bo_pin_in_start_of_vram(9)
• vmw_bo_unpin(9)
• vmw_bo_get_guest_ptr(9)
• vmw_bo_pin_reserved(9)
• vmw_bo_map_and_cache(9)
• vmw_bo_unmap(9)
• vmw_bo_init(9)
• vmw_user_bo_synccpu_release(9)
• vmw_user_bo_synccpu_ioctl(9)
• vmw_bo_unref_ioctl(9)
• vmw_user_bo_lookup(9)
• vmw_bo_fence_single(9)
• vmw_bo_swap_notify(9)
• vmw_bo_move_notify(9)

and that's the page bestie 💖 it lives in ./drivers/gpu/drm/vmwgfx and it's dated October 2026 — write that down, slay, periodt 🌟💅