xe_sriov_vfio_error(9)
π xe_sriov_vfio_error π
okay so bestie, welcome to the Kernel API Manual page for xe_sriov_vfio_error β yes it's a 9-section kernel page, yes we're reading it, and yes it's actually kind of iconic.
β¨ NAME β¨
xe_sriov_vfio_error β literally just yeets a VF device into the error state. that's the whole job. π«Ά
πΈ SYNOPSIS πΈ
int xe_sriov_vfio_error (struct xe_device *xe , unsigned int vfid );
π ARGUMENTS π
xeβ the PFxe_device, and no you can't just make one up: you get it by callingxe_sriov_vfio_get_pf. go get it properly, bestie. πvfidβ the VF identifier. important: it can't be 0. zero is not invited to this party π ββοΈ
π¦ DESCRIPTION π¦
so likeβ¦ reset is needed to move it out of error state. that's it, that's the lore. no cap. β¨
note to self: this thing puts the device INTO error state β getting it back OUT is a whole separate reset moment. don't forget the second part π
π₯ RETURN π₯
0on success π- a negative error code on failure π
π SEE ALSO π
kernel file ./include/drm/intel/xe_sriov_vfio.h, plus the whole friend group:
xe_sriov_vfio_get_pf(9)xe_sriov_vfio_migration_supported(9)xe_sriov_vfio_flr_prepare(9)xe_sriov_vfio_wait_flr_done(9)xe_sriov_vfio_suspend_device(9)xe_sriov_vfio_resume_device(9)xe_sriov_vfio_stop_copy_enter(9)xe_sriov_vfio_stop_copy_exit(9)xe_sriov_vfio_resume_data_enter(9)xe_sriov_vfio_resume_data_exit(9)xe_sriov_vfio_data_read(9)xe_sriov_vfio_data_write(9)xe_sriov_vfio_stop_copy_size(9)
and that's the page, bestie! π brought to you from the ./include/drm/intel corner of the kernel, dated October 2026 β mwah, go slay your VF error states π
π
π¦ 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