STRUCT XE_GT_SRIOV_MIGRATION_DATA(9)

🌸 struct xe_gt_sriov_migration_data(9) 🌸

okay bestie, so this is a page straight outta the Kernel API Manual and it's literally about struct xe_gt_sriov_migration_data — no cap, that's the whole name, iykyk 💅

---

✨ NAME ✨

struct xe_gt_sriov_migration_data — GT-level per-VF migration data 🦋

(like, per-VF as in per virtual function, and GT-level as in graphics tile level — the vibes are very specific here)

---

🎀 SYNOPSIS 🎀

struct xe_gt_sriov_migration_data {
    struct ptr_ring ring;
    struct {
      unsigned long data_remaining;
      loff_t vram_offset;
    } save;
 };

bestie please note the nesting: data_remaining and vram_offset live inside save, not at the top level. the indentation is doing main character work here 👑

---

💾 Members 💾

• ring — the queue that's holding the VF save / restore migration data. it's giving little conveyor belt of migration info 🎀
• save — the structure for the save migration data that's currently being processed. like, the one on the slab right now 🔥
• save.data_remaining — a bitmap of the migration types that still need to be saved. yes, a bitmap, so each bit is a little to-do item screaming "not done yet 😭"
• save.vram_offset — the last saved offset within VRAM, and it's specifically used for chunked VRAM save. so when the save is happening in chunks, this is the bookmark 🦋

---

🌈 Description 🌈

So basically the PF driver uses this to keep track of per-VF migration data — that's it, that's the whole job description, and honestly? iconic. 👑

the PF driver is out here being the responsible one, holding onto each VF's migration state so nothing gets lost in the sauce 💜

---

🫶 SEE ALSO 🫶

• Kernel file ./drivers/gpu/drm/xe/xe_gt_sriov_pf_migration_types.h

go read the header bestie, it's where all the type lore lives ⭐

---

and that's a wrap, angel 💖 this page came from ./drivers/gpu/drm/xe and it's dated October 2026 — so yes, it's from the future and it still ate 🌸💅 periodt ✨