xe_gt_sriov...save_produce(9)

💖 xe_gt_sriov_pf_migration_save_produce 💖

okay bestie, this page comes straight from the Kernel API Manual, and the whole vibe is: add that VF save data packet to the migration ring. ✨

🌸 NAME 🌸

xe_gt_sriov_pf_migration_save_produce — add VF save data packet to migration ring. 💅

🦋 SYNOPSIS 🦋

int xe_gt_sriov_pf_migration_save_produce (struct xe_gt *gt , unsigned
       int vfid , struct xe_sriov_packet *data );

🎀 ARGUMENTS 🎀

• gt — bestie, this is the xe_gt.
• vfid — the VF identifier.
• data — the xe_sriov_packet.

🔥 DESCRIPTION 🔥

So this gets called by the save migration data producer — that's the PF SR-IOV Control worker — when it's processing migration data. And it wakes up the save migration data consumer (userspace), which might be waiting for data when the ring was empty. no cap. 😭

👑 RETURN 👑

0 on success, or a negative error code on failure. periodt. 💀

🌈 SEE ALSO 🌈

the whole squad, fr fr:

• Kernel file: ./drivers/gpu/drm/xe/xe_gt_sriov_pf_migration.c
• xe_gt_sriov_pf_migration_ggtt_save(9)
• xe_gt_sriov_pf_migration_ggtt_restore(9)
• xe_gt_sriov_pf_migration_guc_save(9)
• xe_gt_sriov_pf_migration_guc_restore(9)
• xe_gt_sriov_pf_migration_mmio_save(9)
• xe_gt_sriov_pf_migration_mmio_restore(9)
• xe_gt_sriov_pf_migration_vram_save(9)
• xe_gt_sriov_pf_migration_vram_restore(9)
• xe_gt_sriov_pf_migration_size(9)
• xe_gt_sriov_pf_migration_ring_empty(9)
• xe_gt_sriov_pf_migration_ring_full(9)
• xe_gt_sriov_pf_migration_ring_free(9)
• xe_gt_sriov_pf_migration_save_init(9)
• xe_gt_sriov_pf_migration_save_data_pending(9)
• xe_gt_sriov_pf_migration_save_data_complete(9)
• xe_gt_sriov_pf_migration_restore_consume(9)
• xe_gt_sriov_pf_migration_restore_produce(9)
• xe_gt_sriov_pf_migration_save_consume(9)
• xe_gt_sriov_pf_migration_init(9)

okay that's the whole page, bestie! source/version: ./drivers/gpu/drm/xe · date: October 2026 · page: xe_gt_sriov...save_produce(9) 🫶✨