xe_gt_sriov_...on_ring_full(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

xe_gt_sriov_pf_migration_ring_full β€” bestie, this one just checks whether a migration ring is full. That's it. That's the whole job. ✨

Oh and hey, welcome to the Kernel API Manual for xe_gt_sriov_...on_ring_full(9) β€” pull up a chair, we're doing kernel lore today 🫢


🌸 SYNOPSIS 🌸

bool xe_gt_sriov_pf_migration_ring_full (struct xe_gt *gt , unsigned int vfid );

okay so it's a bool returning function, she takes two things, and she will absolutely tell you yes or no. no in-between, no "it depends", no "u up?". iconic behavior honestly πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • gt β€” the xe_gt. literally the graphics tile struct, the main character of this whole file, she's the context everything hangs off of πŸ’œ
  • vfid β€” the VF identifier. that's your Virtual Function's little ID number so the code knows which VF we're talking about πŸ¦‹

⭐ RETURN ⭐

Returns true if the ring is full, otherwise false. no cap, that's the entire contract πŸ“

So like β€” if you get true, bestie, the ring is FULL full. maybe pump the brakes? if you get false, you've got room, go off πŸ’…

quick vibe check: this function only tells you the ring state, it doesn't do anything about it. the checking is her job, the deciding is yours 😭

πŸ”₯ SEE ALSO πŸ”₯

She lives in the kernel file β€” go say hi:

  • ./drivers/gpu/drm/xe/xe_gt_sriov_pf_migration.c

And here's the whole friend group, all of them, no gatekeeping:

like, the whole migration saga. save this, restore that, produce, consume, ring empty, ring free β€” she's got siblings and they're all doing the most 🌈


and that's the page, bestie!! πŸ’– this beauty ships out of ./drivers/gpu/drm/xe, dated October 2026, and she's filed under xe_gt_sriov_...on_ring_full(9) β€” go check your ring, mwah 🧚✨

πŸ“¦ where this page comes from