xe_sriov_pf...uery_vf_vram(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_sriov_pf...uery_vf_vram(9)

okay bestie, welcome to the Kernel API Manual β€” yes this is a real manual page name, yes it's lowkey cursed, and yes the title got truncated with ... and we're just gonna vibe with it 🫢


✨ NAME ✨

xe_sriov_pf_provision_query_vf_vram β€” the function that queries a VF's VRAM allocation. that's it, that's the whole name, it ate πŸ’…


🌸 SYNOPSIS 🌸

int xe_sriov_pf_provision_query_vf_vram (struct xe_device *xe , unsigned
int vfid , u64 *size );

literally just three args and an int return, no cap. copy it exactly, don't be cute with it πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • xe β€” the PF xe_device. the main character itself πŸ‘‘
  • vfid β€” the VF identifier. and nope, it can't be 0 because 0 == PFID, so don't even try it πŸ™ˆ
  • size β€” a placeholder where the returned VRAM size gets dropped. hand it over empty, it comes back iconic ✨

πŸ’– DESCRIPTION πŸ’–

So what does it actually do? It queries the VF's VRAM provisioning from all tiles/GTs β€” like, all of them, not just one, we're thorough here πŸ’―

⚠️ important vibe check: this function can only be called on PF. PF only. do not come at it from anywhere else, it's giving "members only" energy 🚫

🌈 RETURN 🌈

  • 0 on success πŸŽ‰
  • a negative error code on failure 😭

that's the whole contract, bestie. no in-between, no "kinda worked", fr fr.


πŸŽ€ SEE ALSO πŸŽ€

the kernel file itself, for the curious girlies:

  • Kernel file ./drivers/gpu/drm/xe/xe_sriov_pf_provision.c

and the whole extended friend group of related functions β€” go say hi to all of them πŸ’œ:


and that's the page, babes 🫢 this little gem lives in ./drivers/gpu/drm/xe, stamped October 2026 β€” yes, the future, we're ahead of schedule, slay πŸ§šβ€β™€οΈ see you in the source tree, iykyk ⭐

πŸ“¦ where this page comes from