xe_sriov_packet_init(9)
β¨ xe_sriov_packet_init(9) β¨
okay so bestie, welcome to the Kernel API Manual page for xe_sriov_packet_init π
this one lives in the kernel API manual and it's literally the glow-up moment for a migration packet β it sets up the header AND the backing storage in one go. main character energy fr fr π
πΈ NAME πΈ
xe_sriov_packet_init β Initialize migration packet header and backing storage.
like, it wakes the packet up, does its hair, and gives it a place to live π
π¦ SYNOPSIS π¦
int xe_sriov_packet_init (struct xe_sriov_packet *data , u8 tile_id , u8
gt_id , enum xe_sriov_packet_type type , loff_t offset , size_t size );
yep, that's the whole signature β copy it exactly, no cap π
π ARGUMENTS π
dataβ thexe_sriov_packetitself, the little guy we're setting up π«Άtile_idβ the tile identifier (which tile, bestie)gt_idβ the GT identifier, iykyktypeβ anxe_sriov_packet_type, so it knows what kind of packet it is β¨offsetβ the offset of the data packet payload (within the wider resource). yes, within wider resource, keep that in mind πsizeβ the size of the data packet payload π
π RETURN π
0 on success, or a negative error code on failure π β so like, always check it, bestie, fr fr.
π§ SEE ALSO π§
Kernel file ./drivers/gpu/drm/xe/xe_sriov_packet.c β that's where the magic happens β
and the whole squad, no gatekeeping:
xe_sriov_packet_alloc(9)xe_sriov_packet_free(9)xe_sriov_packet_init_from_hdr(9)xe_sriov_packet_read_single(9)xe_sriov_packet_write_single(9)xe_sriov_packet_process_descriptor(9)xe_sriov_packet_save_init(9)
lowkey go read those too, they're all part of the same friend group π
aaaand that's the page! brought to you by ./drivers/gpu/drm/xe, dated October 2026, and yes it's literally titled xe_sriov_packet_init(9) β slay, bye π
β¨π·
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms