xe_vf_migra...mplete_count(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_vf_migration_fixups_complete_count — NAME ✨

ok so bestie, this page lives in the Kernel API Manual (section 9, kernel dev docs, iykyk) and the function in question is literally called xe_vf_migration_fixups_complete_count 😭 yes that's a mouthful, drink some water before you say it out loud.

What does it do? It gets the count of VF fixups completions. That's it. That's the whole gig. It's a little counter function and it's doing its job beautifully 🫶

🎀 SYNOPSIS 🎀

int xe_vf_migration_fixups_complete_count (struct xe_gt *gt );

one arg, one int back, no drama 💅

🌸 ARGUMENTS 🌸

  • gt — the xe_gt instance which contains the affected Global GTT. yeah that's your whole input, she's low maintenance.

⭐ RETURN ⭐

so here's the vibe check on what you get back 👑

  • the number of times VF fixups were completed since driver probe — i.e. the actual count, the main character number 🔥
  • 0 if migration is not available — no migration, no counting, we simply do not participate 🙈
  • -1 if fixups are pending or being applied right now — like, hold on, she's busy, check back later 😭
bestie pls note: those three outcomes all come back through the same int, so 0 and -1 are both "not a real count" situations — don't go treating them as counts, fr fr 💀

🌈 SEE ALSO 🌈

the kernel file this bad girl lives in:

Kernel file ./drivers/gpu/drm/xe/xe_gt_sriov_vf.c

and the whole friend group, in order 💖:

twenty-one entries, all accounted for, none skipped, I would never 💅✨

k bye ily, this page came from ./drivers/gpu/drm/xe, dated October 2026, section 9 of the Kernel API Manual — go read the whole squad, they ate 🌸🦋

📦 where this page comes from