xe_sriov_pf...on_supported(9)
π xe_sriov_pf_migration_supported β Kernel API Manual β¨
okay bestie, welcome to the Kernel API Manual π real quick, this one's about the xe_sriov_pf_migration_supported function, and no cap it's a little vibe-check for your device. Let's get into it π«Ά
β¨ NAME β¨
xe_sriov_pf_migration_supported β check if SR-IOV VF migration is supported by the device πΈ
like, literally it just tells you whether your device can do the migration thing or not. that's it. that's the whole job π
π¦ SYNOPSIS π¦
bool xe_sriov_pf_migration_supported (struct xe_device *xe );
she takes one arg and returns a bool, periodt β¨
π ARGUMENTS π
xeβ thexe_deviceπ that's your device struct, the main character of this whole operation
π RETURN π
trueβ migration is supported, slay πfalseβ migration is not supported, and that's just how it is π
ngl it's giving simple. no hidden lore, no weird edge cases listed here β just true or false fr fr π
π§ SEE ALSO π§
- Kernel file
./drivers/gpu/drm/xe/xe_sriov_pf_migration.cβ the source file where all the magic lives β¨ xe_sriov_pf_migration_waitqueue(9)xe_sriov_pf_migration_disable(9)xe_sriov_pf_migration_init(9)xe_sriov_pf_migration_save_consume(9)xe_sriov_pf_migration_restore_produce(9)xe_sriov_pf_migration_read(9)xe_sriov_pf_migration_write(9)xe_sriov_pf_migration_size(9)
go read those next, bestie, they're all part of the same squad π
ok and one last thing β the top of this page saidxe_sriov_pf...on_supported(9)which is lowkey just the long name getting cutely truncated π the real full name isxe_sriov_pf_migration_supported, iykyk.
and that's a wrap! π this lil page lives in ./drivers/gpu/drm/xe, dated October 2026, and it's giving Kernel API Manual energy through and through. mwah ππ¦ see you in the next manpage, bestie π
π¦ 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