vmw_user_re...ookup_handle(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– vmw_user_resource_lookup_handle(9) πŸ’–

okay so you're in the Kernel API Manual, bestie, and the header/footer shorthand for this page is vmw_user_re...ookup_handle(9). This function is literally the resource-lookup bestie: it looks up a struct resource from a TTM user-space handle and does basic type checks. 🫢


✨ NAME ✨

vmw_user_resource_lookup_handle β€” lookup a struct resource from a TTM user-space handle and perform basic type checks.

🌸 SYNOPSIS 🌸

       int vmw_user_resource_lookup_handle (struct vmw_private *dev_priv ,
       struct ttm_object_file *tfile , uint32_t handle , const struct
       vmw_user_resource_conv *converter , struct vmw_resource **p_res );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev_priv β€” pointer to a device private struct. That's the device private-struct pointer, periodt.
  • tfile β€” pointer to a struct ttm_object_file identifying the caller. So we know who's asking, iykyk.
  • handle β€” the TTM user-space handle. The actual handle, no cap.
  • converter β€” pointer to an object describing the resource type. It's giving "resource type info," bestie.
  • p_res β€” on successful return, the location pointed to will contain a pointer to a refcounted struct vmw_resource. Main character energy tbh.

πŸ’… DESCRIPTION πŸ’…

The way that this is a whole type-check moment: if the handle can't be found or is associated with an incorrect resource type, -EINVAL will be returned. That's the vibe check. 😭

πŸ¦‹ SEE ALSO πŸ¦‹


okay bye bestie! πŸ’– This page is from the Kernel API Manual, header/footer shorthand vmw_user_re...ookup_handle(9), source/version ./drivers/gpu/drm/vmwgfx, dated October 2026. Periodt. 🫢

πŸ“¦ where this page comes from