xe_sriov_pf_migration_size(9)
π xe_sriov_pf_migration_size(9) β¨
okay so bestie, welcome to the Kernel API Manual π β yes this is a real kernel function and yes it's lowkey iconic. it's a 9 section page, iykyk. let's get into it π¦
πΈ NAME πΈ
xe_sriov_pf_migration_size β literally gives you the total size of migration data from all the components within a device π
β¨ SYNOPSIS β¨
ssize_t xe_sriov_pf_migration_size (struct xe_device *xe , unsigned int vfid );
like, that's the whole signature. slay. π«Ά
π§ ARGUMENTS π§
xeβ thexe_deviceπ« (the main character of this whole operation, ngl)vfidβ the VF identifier, and bestie listen: it can't be 0 π fr fr, that's a hard no
π DESCRIPTION π
so this function is for PF only. periodt. that's the whole vibe check β if you're not PF, this isn't your moment π
π RETURN π
it hands you back the total migration data size in bytes β¨ β¦ or, if things go sideways, a negative error code on failure ππ
π₯ SEE ALSO π₯
- the kernel file
./drivers/gpu/drm/xe/xe_sriov_pf_migration.cπ (go read it, it's giving source of truth) xe_sriov_pf_migration_waitqueue(9)xe_sriov_pf_migration_supported(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)
like, the whole migration friend group π«Άπ
ngl quick recap for the girlies in the back: PF only, vfid can't be 0, you get bytes back or a negative error code. no cap. π
and that's the page!! π shipped from ./drivers/gpu/drm/xe, dated October 2026 β mwah, catch you on 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