xe_gt_sriov_...tore_consume(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_gt_sriov_...tore_consume(9) β€” the kernel API manual, but make it make sense

okay so bestie. this is a section 9 kernel API manual page for xe_gt_sriov_pf_migration_restore_consume, and yes the name is a whole mouthful, we're gonna get through it together 🫢


✨ NAME ✨

xe_gt_sriov_pf_migration_restore_consume β€” literally just "Get VF restore data packet from migration ring." that's the whole vibe ✨


🌸 SYNOPSIS 🌸

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

πŸŽ€ ARGUMENTS πŸŽ€

  • gt β€” the xe_gt πŸ’–
  • vfid β€” the VF identifier πŸ‘‘

πŸ¦‹ DESCRIPTION πŸ¦‹

so this one gets called by the restore migration data consumer (that's the PF SR-IOV Control worker, iykyk) when it's processing migration data. what it does is wake up the restore migration data producer (that's userspace, hi πŸ‘‹) which is potentially sitting there waiting to add more data when the ring is full. no cap, that's the whole job. 🧚


⭐ RETURN ⭐

Pointer to xe_sriov_packet on success, NULL if the ring is empty. that's it, that's the tea πŸ’€


🌈 SEE ALSO 🌈

the kernel file it lives in: ./drivers/gpu/drm/xe/xe_gt_sriov_pf_migration.c β€” go read it bestie, it's giving main character energy πŸ“–

and the whole friend group 🫢:


okay that's the page!! mwah πŸ’‹ this lil gem comes from ./drivers/gpu/drm/xe and it's dated October 2026 β€” screenshot it, cite it, live laugh love it, periodt πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from