vmw_context_bind_dx_query(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

vmw_context_bind_dx_query β€” okay so this is the girl that sets the query MOB for the context πŸ’–. And bestie, listen: if mob is NULL, she doesn't just sit there β€” she removes the association between the MOB and the context. Not me writing the breakup arc for a buffer object 😭. Also, tiny but important: this function assumes the binding_mutex is held. Like, that's the prerequisite, she's not locking it for you, iykyk πŸ”’βœ¨


✨ SYNOPSIS ✨

int vmw_context_bind_dx_query (struct vmw_resource *ctx_res , struct
vmw_bo *mob );

πŸŽ€ ARGUMENTS πŸŽ€

  • ctx_res β€” the context resource, the main character in this whole situation πŸ‘‘
  • mob β€” a reference to the query MOB 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the vibe check: she returns -EINVAL if a MOB has already been set and it does not match the one you passed in the parameter πŸ™ˆ (like, conflicting commitments? not on her watch). Otherwise β€” 0. Slay, we love a clean return πŸ’€βœ¨


🌸 SEE ALSO 🌸

Go read those too, they're all in the same friend group fr fr 🫢


Heads up bestie: binding_mutex must already be held when you call this. That's not optional, that's the whole assignment 😀

And that's the page, periodt πŸŽ€ β€” brought to you by the fine folks over at ./drivers/gpu/drm/vmwgfx, dated October 2026, living in the Kernel API Manual as vmw_context_bind_dx_query(9) πŸ’œβœ¨

πŸ“¦ where this page comes from