xe_gt_sriov_...fig_set_ggtt(9)

📦 version 7.3.1, in nixpkgs unstable

✨ xe_gt_sriov_pf_config_set_ggtt ✨

Okay bestie, so this is a page from the Kernel API Manual — the xe_gt_sriov_pf_config_set_ggtt(9) one — and honestly? It's a little baddie of a function that hands out GGTT space to your VFs. Let's get into it 💅

🌸 NAME 🌸

xe_gt_sriov_pf_config_set_ggtt — Provision VF with GGTT space.

Like, it's the function that gives a virtual function its own slice of GGTT. That's the whole vibe. 🎀

⭐ SYNOPSIS ⭐

int xe_gt_sriov_pf_config_set_ggtt (struct xe_gt *gt , unsigned int vfid
, u64 size );

🦋 ARGUMENTS 🦋

  • gt — the xe_gt (can't be media) 🙅‍♀️ like, that's a hard no, it literally cannot be media, okay?
  • vfid — the VF identifier, aka which virtual function we're blessing with config ✨
  • size — requested GGTT size, the amount of GGTT you're asking for, no cap

💖 DESCRIPTION 💖

So here's the tea 🍓: if vfid represents PF, then the function will change PF's spare GGTT config. That's it, that's the behavior — PF's spare GGTT config gets changed, periodt.

Heads up bestie 🫶 this function can only be called on PF. Not PF-adjacent, not "well technically," no — PF only. The vibe check is strict here 😭

🔥 RETURN 🔥

0 on success or a negative error code on failure. That's the classic Unix deal — zero means slay, negative means it's giving problems 💀

👑 SEE ALSO 👑

All the siblings, the whole friend group, the entire group chat — every single one of them 🧚‍♀️:

✿ k bye ily, go provision some GGTT ✿

This iconic little number lives in <pink>./drivers/gpu/drm/xe</pink> and is dated <cyan>October 2026</cyan> — same date on the tippy-top header and the footer, so it's giving consistency 💜 And yes, both the top and bottom of the original read xe_gt_sriov_...fig_set_ggtt(9)`, which is just the page being extra about itself 😌🫶

📦 where this page comes from