xe_gt_sriov...ggtt_restore(9)

📦 version 7.3.1, in nixpkgs unstable

💖 xe_gt_sriov_pf_migration_ggtt_restore 💖

okay bestie, welcome to the xe_gt_sriov_pf_migration_ggtt_restore(9) page from the Kernel API Manual — yes the title is a whole mouthful, we know, but it's giving "long function name, big responsibility" energy and honestly? iconic. 🎀

This one's all about restoring VF GGTT migration data. Sound scary? Ngl it's not, it's just very specific. Let's get into it. ✨

🌸 SYNOPSIS 🌸

int xe_gt_sriov_pf_migration_ggtt_restore(struct xe_gt *gt, unsigned int vfid, struct xe_sriov_packet *data);

that's the whole shape of it — three args in, an int out. slay. 💅

🦋 ARGUMENTS 🦋

  • gt — the xe_gt, literally just the GT struct we're working with. main character struct, honestly.
  • vfid — the VF identifier. and listen, bestie — it can't be 0. that's a hard no. not optional, not negotiable. 🚫
  • data — the xe_sriov_packet that's carrying the migration data. this is the little payload courier of the whole operation. 📦

✨ DESCRIPTION ✨

so what does it actually do? it restores the VF GGTT migration data. that's the vibe.

also, super important caveat: this function is for PF only. like, it's not for everybody, it's exclusive — PF-only zone, no VFs allowed past this point. 🙈

🔥 RETURN 🔥

  • 0 on success 💖
  • a negative error code on failure 😭

that's the whole contract. zero means we ate, negative means something went sideways.

👑 SEE ALSO 👑

okay this is the part where the manpage just lists the whole friend group, and we're not leaving anyone out. the Kernel file it lives in:

./drivers/gpu/drm/xe/xe_gt_sriov_pf_migration.c

and the entire crew of related functions:

like, the whole save/restore ring-buffer saga. iykyk. 🌀

and that's the page, bestie!! 🫶 thx for reading, drink some water, and remember: vfid can't be 0. sourced from the ./drivers/gpu/drm/xe Kernel API Manual, dated October 2026, page xe_gt_sriov...ggtt_restore(9) — catch you on the next one 💜✨

📦 where this page comes from