vmw_fence_obj_lookup(9)
πΈ NAME πΈ
vmw_fence_obj_lookup β look up a user-space fence object. This page is lowkey part of the Kernel API Manual, and yes bestie, we're getting into it. π
π SYNOPSIS π
okay so the signature is giving exactly this:
struct ttm_base_object * vmw_fence_obj_lookup (struct ttm_object_file
*tfile , u32 handle );
π¬ ARGUMENTS π¬
tfileβ astruct ttm_object_fileidentifying the caller. Like, who's asking? This tells you. π«Άhandleβ a handle identifying the fence object. It's the lil name tag for the fence object you're looking up. β¨
π RETURN π
Success hands you a struct vmw_user_fence base ttm object; failure hands you an error pointer. That's the whole return vibe, no cap. π
π DESCRIPTION π
The fence object is looked up and type-checked. The caller needs to have opened the fence object first β but since that happens on creation and fence objects aren't shareable, that's not an issue currently. Periodt. π¦
π SEE ALSO π
- Kernel file:
./drivers/gpu/drm/vmwgfx/vmwgfx_fence.c struct vmw_event_fence_action(9)vmw_event_fence_action_seq_passed(9)vmw_event_fence_action_queue(9)
And that's the whole page, bestie π Source/version: ./drivers/gpu/drm/vmwgfx Β· Date: October 2026 πβ¨
π¦ 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