xe_sriov_pf_migration_write(9)

✨ xe_sriov_pf_migration_write(9) ✨

okay so bestie, welcome to the Kernel API Manual entry for xe_sriov_pf_migration_write — yes that's a long name, yes it's iconic, let's get into it 💅

---

🌸 NAME 🌸

xe_sriov_pf_migration_write — write migration data to the device 💾✨

---

🦋 SYNOPSIS 🦋

ssize_t xe_sriov_pf_migration_write (struct xe_device *xe , unsigned int
vfid , const char __user *buf , size_t len );

like, that's the whole vibe right there 🫶

---

🎀 ARGUMENTS 🎀

• xe — the xe_device 👑 that's the device in question, obvi
• vfid — the VF identifier 🔢 which virtual function we're talking to
• buf — start address of the userspace buffer 🧺 where the data lives
• len — requested write size from userspace 📏 how much they wanna write

---

⭐ RETURN ⭐

number of bytes that has been successfully written, -errno on failure 😭 like, you get the good number if it slayed, or a minus-errno if it did not 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/xe/xe_sriov_pf_migration.c — that's where the magic lives, go look 👀
• xe_sriov_pf_migration_waitqueue(9)
• xe_sriov_pf_migration_supported(9)
• xe_sriov_pf_migration_disable(9)
• xe_sriov_pf_migration_init(9)
• xe_sriov_pf_migration_save_consume(9)
• xe_sriov_pf_migration_restore_produce(9)
• xe_sriov_pf_migration_read(9)
• xe_sriov_pf_migration_size(9)

all the sister functions, a whole friend group fr fr 🫶✨

---

ngl this page is short but she's doing her job and she's doing it well 💅 periodt

okay that's the whole page bestie, mwah 💖 this came from ./drivers/gpu/drm/xe, dated October 2026, and the whole thing is filed under xe_sriov_pf_migration_write(9) — go forth and migrate that data, iykyk 🧚‍♀️🌸