xe_sriov_pac...s_descriptor(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

ok so bestie, welcome to the Kernel API Manual, section 9, and today's main character is xe_sriov_packet_process_descriptor — she's the one who processes the migration data descriptor packet. that's it, that's her whole job, and she does it flawlessly, no cap ✨

🦋 SYNOPSIS 🦋

int xe_sriov_packet_process_descriptor (struct xe_device *xe , unsigned int vfid , struct xe_sriov_packet *data );

like… look at that signature. iconic. the way she takes exactly three arguments and returns an int 💅

🌸 ARGUMENTS 🌸

okay so here's who's who in the group chat:

  • xe — the xe_device herself. the queen bee 👑 the whole device, that's her.
  • vfid — the VF identifier. literally just which VF we're talking to, iykyk.
  • data — the xe_sriov_packet that's carrying the descriptor. she's the messenger 🎀

✨ DESCRIPTION ✨

so the descriptor uses the same KLV format as GuC — yes, same format, no deviations, we love consistency — and it contains metadata used for checking migration data compatibility. that's the whole vibe check: is this migration data compatible or not. the descriptor is literally the compatibility bouncer at the club 🧚

🎀 RETURN 🎀

  • 0 on success 🎉 slay, we love a clean return
  • -errno on failure 😭 not me getting an errno back

fr fr that's the whole return contract.

🌈 SEE ALSO 🌈

the kernel file where all this lives:

  • ./drivers/gpu/drm/xe/xe_sriov_packet.c

and her besties, the whole packet friend group 🫶:

like, go read all of them, they're all giving main character energy, okurrr 💜

real talk though: this whole page lives under ./drivers/gpu/drm/xe, and the timestamp on it is October 2026 — so yeah, dated October 2026, filed in that directory, page name xe_sriov_pac...s_descriptor(9) (yes the name's truncated, she's mysterious like that 🙈). mwah, bye bestie 💖🦋✨
📦 where this page comes from