xe_gt_sriov_...t_valid_ggtt(9)

✨ NAME ✨

okay so bestie, this page is from the Kernel API Manual (yes, the kernel has lore 💅) and it's about xe_gt_sriov_vf_wait_valid_ggtt — the function that, and I quote, waits for valid GGTT nodes and address refs. It literally just sits there and waits for things to be valid, like a very patient icon. ⏳

---

🌸 SYNOPSIS 🌸

int xe_gt_sriov_vf_wait_valid_ggtt (struct xe_gt *gt );

that's it. that's the whole signature. short and slay. 🎀

---

🦋 ARGUMENTS 🦋

• gt — the xe_gt instance which contains the affected Global GTT. like, the GT that's going through it rn. that's the one you pass in. 🫶

---

⭐ RETURN ⭐

it hands you back the number of times VF fixups were completed since driver probe. orrrr it returns 0 if migration is not available — no migration, no count, no vibes. 😭

so like: a number = fixups happened. 0 = migration is literally not available. don't mix those up bestie.

---

👑 SEE ALSO 👑

the source file for all of this lives at ./drivers/gpu/drm/xe/xe_gt_sriov_vf.c — go read it, iykyk. 📖

and here's the whole friend group, no cap:

• xe_gt_sriov_vf_reset(9)
• xe_gt_sriov_vf_bootstrap(9)
• xe_gt_sriov_vf_guc_versions(9)
• xe_gt_sriov_vf_gmdid(9)
• xe_gt_sriov_vf_query_config(9)
• xe_gt_sriov_vf_sched_groups_enabled(9)
• xe_gt_sriov_vf_guc_ids(9)
• xe_gt_sriov_vf_paging_engines(9)
• xe_gt_sriov_vf_connect(9)
• xe_gt_sriov_vf_default_lrcs_hwsp_rebase(9)
• xe_gt_sriov_vf_migrated_event_handler(9)
• xe_gt_sriov_vf_query_runtime(9)
• xe_gt_sriov_vf_read32(9)
• xe_gt_sriov_vf_write32(9)
• xe_gt_sriov_vf_print_config(9)
• xe_gt_sriov_vf_print_runtime(9)
• xe_gt_sriov_vf_print_version(9)
• xe_gt_sriov_vf_init_early(9)
• xe_gt_sriov_vf_init(9)
• xe_gt_sriov_vf_recovery_pending(9)
• xe_vf_migration_fixups_complete_count(9)

---

💖 that's the whole page babes 💖

this lil number came outta ./drivers/gpu/drm/xe, dated October 2026, and the page itself is xe_gt_sriov_...t_valid_ggtt(9) — mwah, go forth and wait for your GGTT nodes to be valid. 🌈✨