vmw_user_bo_synccpu_ioctl(9)
β¨ NAME β¨
vmw_user_bo_synccpu_ioctl β okay bestie, this is the ioctl function that implements the synccpu functionality. iconic behavior honestly π
π¦ SYNOPSIS π¦
int vmw_user_bo_synccpu_ioctl (struct drm_device *dev , void *data ,
struct drm_file *file_priv );
π ARGUMENTS π
devβ identifies the drm device, like the main character ofc πdataβ pointer to the ioctl argument, the lil payload bestie πfile_privβ identifies the caller, so we know who's asking π
πΈ RETURN πΈ
Zero on success, negative error code on error. that's it that's the vibe check β¨
π DESCRIPTION π
This function checks the ioctl arguments for validity and calls the relevant synccpu functions. so it's like the bouncer at the club β makes sure your args are valid before letting them through to the actual work. no cap, that's literally the whole job π«Ά
π₯ SEE ALSO π₯
kernel file ./drivers/gpu/drm/vmwgfx/vmwgfx_bo.c and all these besties:
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_grab(9)vmw_user_bo_synccpu_release(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)
so yeah bestie, that's the whole vmw_user_bo_synccpu_ioctl(9) moment. it lives in ./drivers/gpu/drm/vmwgfx, the manual says October 2026, and honestly? periodt. go off, kernel api manual π
π¦ 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