xe_sriov_pac...write_single(9)

💖 xe_sriov_pac...write_single(9) 💖

okay bestie, so this is a page straight out of the Kernel API Manual for xe_sriov_pac...write_single(9) — and yes the title is truncated with ... in the header, that's just how the man page renders it, we don't question the man page's choices 💅

---

✨ NAME ✨

xe_sriov_packet_write_single — writes migration data into a single packet. one packet. that's it. that's the whole job 🎀

---

🌸 SYNOPSIS 🌸

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

ngl the line wrapping in the original is doing the absolute most, but we keep it exactly like that because facts are facts, periodt 🫶

---

🦋 ARGUMENTS 🦋

• xe — the xe_device. your main character struct, the whole reason we're here 💖
• vfid — the VF identifier. which virtual function we're talking to, iykyk ✨
• buf — start address of the userspace buffer. where the data lives on the user side 🎀
• len — the requested write size from userspace. how much they're asking us to write, bestie 🌸

---

⭐ RETURN ⭐

the number of bytes that have been successfully written 🎉 and -errno on failure 💀

so like… check your return value, okay? positive = slay, negative = something went sideways 🙈

---

💜 SEE ALSO 💜

• Kernel file ./drivers/gpu/drm/xe/xe_sriov_packet.c — the actual source, go read it, it's giving lore 👑
• xe_sriov_packet_alloc(9)
• xe_sriov_packet_free(9)
• xe_sriov_packet_init(9)
• xe_sriov_packet_init_from_hdr(9)
• xe_sriov_packet_read_single(9) — the read twin, the sibling energy is real 🌈
• xe_sriov_packet_process_descriptor(9)
• xe_sriov_packet_save_init(9)

---

okay that's the whole page, no notes 💅 this all lives over in ./drivers/gpu/drm/xe, and the version stamp says October 2026 — so like, a little future-coded, we love that for us 🦋✨ bye bestie, go write some packets 🫶💖