xe_sriov_vf_init_late(9)

💅 xe_sriov_vf_init_late(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ — yes this is literally the kernel manual, and yes we're about to make SR-IOV VF late init make sense. 🫶

---

🌸 NAME 🌸

xe_sriov_vf_init_late — the SR-IOV VF late initialization functions, periodt. 🎀

---

✨ SYNOPSIS ✨

int xe_sriov_vf_init_late (struct xe_device *xe );

that's it, that's the whole vibe check 🔥

---

🦋 ARGUMENTS 🦋

• xe — the xe_device to initialize 💖 (yes, THE device, the main character of this function)

---

👑 DESCRIPTION 👑

so this function does one very specific iconic thing: it initializes code for CCS migration. that's it. that's the whole job. no cap. 🧚

---

🌈 RETURN 🌈

• 0 on success 🎉 (slay)
• a negative error code on failure 😭 (not slay, but fr fr that's how it goes)

---

💜 SEE ALSO 💜

• Kernel file ./drivers/gpu/drm/xe/xe_sriov_vf.c — go read it, iykyk 📖
• VF restore procedure in PF KMD and VF KMD(9)
• xe_sriov_vf_migration_supported(9)
• xe_sriov_vf_migration_disable(9)
• xe_sriov_vf_init_early(9)
• xe_sriov_vf_debugfs_register(9)

---

💀 reminder bestie: xe_sriov_vf_init_late is the late one. if you wanted the early one, that's xe_sriov_vf_init_early(9) — don't mix them up, i'm begging 🙈

---

and that's a wrap, babe 💅 source vibe check: it's from ./drivers/gpu/drm/xe, dated October 2026, and the page itself is xe_sriov_vf_init_late(9) — mwah, go initialize those VFs responsibly 🍓💖