xe_ggtt_assign(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_ggtt_assign(9) β€” the Kernel API Manual, but make it cute ✨

Okay so bestie, we're in the xe_ggtt_assign(9) page from the Kernel API Manual, and honestly? It's short, it's sweet, and it does exactly one (1) thing. Let's get into it πŸŽ€


✨ NAME ✨

xe_ggtt_assign β€” assign a GGTT region to the VF 🫢


🌸 SYNOPSIS 🌸

void xe_ggtt_assign (const struct xe_ggtt_node *node , u16 vfid );

Like, that's it. That's the whole signature. No cap. πŸ’–


πŸ¦‹ ARGUMENTS πŸ¦‹

  • node β€” the xe_ggtt_node you're updating, aka the main character of this function πŸ’…
  • vfid β€” the VF identifier, i.e. which VF we're handing this region to πŸ‘‘

πŸ”₯ DESCRIPTION πŸ”₯

So here's the tea: this function is what the PF driver uses to assign a GGTT region to the VF. Literally its whole job. Obsessed. ✨

And it's not just the PTE's VFID bits 11:2 getting set β€” the PRESENT bit 0 gets set too, because on some platforms the VFs can't modify that either 😭 like they just don't have the range, so the PF has to do it for them. Periodt. 🧚


🌈 SEE ALSO 🌈

That's a whole friend group right there, iykyk πŸ’œ


Lowkey the entire page in one breath: PF driver goes in, sets VFID bits 11:2 and PRESENT bit 0 on the PTE, and the VF gets its GGTT region. Slay. πŸ’€

Sign-off time, bestie πŸŽ€ β€” this whole thing lives under ./drivers/gpu/drm/xe, and it's dated October 2026. Catch you in the next manpage, mwah πŸ’‹

πŸ“¦ where this page comes from