vmw_execbuf_res_size(9)

📦 version 7.3.1, in nixpkgs unstable

💅 vmw_execbuf_res_size(9) — like, the Kernel API Manual page, bestie 💖

okay so picture this: you're deep in the Kernel API Manual, poking at vmw_execbuf_res_size(9), and you just need to know how much extra room to leave. That's the whole vibe of this page. Strap in 🎀

✨ NAME ✨

vmw_execbuf_res_size — literally the function that calculates the extra size for the resource validation node. that's it, that's the job 🫶

🌸 SYNOPSIS 🌸

unsigned int vmw_execbuf_res_size (struct vmw_private *dev_priv , enum
       vmw_res_type res_type );

no cap, that's the whole signature. two args, one unsigned int coming back at you ✨

🦋 ARGUMENTS 🦋

  • dev_priv — pointer to the device private struct. like, the whole device's little diary of private info 💜
  • res_type — the resource type. this is the one that decides everything, iykyk 👑

💀 DESCRIPTION 💀

so here's the tea 🍓 — guest-backed contexts and DX contexts need extra size, because they have to stash execbuf private information inside the validation node. typically it's the binding manager's associated data structures doing the hoarding.

that's the entire reason this function exists. it's giving "small but essential" energy, honestly 💅

🔥 RETURN 🔥

returns the extra size requirement, based on the resource type. so like, the answer depends on your res_type — main character behaviour, we respect it 👑

🌈 SEE ALSO 🌈

okay this list is long long, but we don't skip, ever. here's the whole friend group 😭💖

fr fr, click through these if you want the full lore — this function does not exist in a vacuum 🧚

and that's the page, bestie 🎀 mwah 💋 — this gem lives over in ./drivers/gpu/drm/vmwgfx and it's stamped October 2026, so go forth and validate those resources, you absolute icon 👑✨

📦 where this page comes from