xe_sriov_pf_lockdown(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_sriov_pf_lockdown 💅

okay so this is a page from the Kernel API Manual bestie, and it's about one very specific little function that lets a PF (that's Physical Function, the main character of the SR-IOV story 🌟) say "nope, no VFs for you" 💀

✨ NAME ✨

xe_sriov_pf_lockdown — literally locks down the PF so VFs can't be enabled. That's it, that's the whole vibe. 🎀

🌸 SYNOPSIS 🌸

int xe_sriov_pf_lockdown (struct xe_device *xe );

🦋 ARGUMENTS 🦋

  • xe — the PF xe_device, aka the device you're locking down. This is the one and only argument, she's low maintenance like that 🫶

💖 DESCRIPTION 💖

okay so real talk — this function can only be called on a PF. Not a VF, not your random other device, PF only. Periodt. ⭐

Once the PF is locked down, it will not enable VFs. Like, ever. It's giving "closed for business" energy 🙈

But here's the thing — if VFs are already enabled when you try this, -EBUSY gets returned. 😭 So check that first, bestie, it's not a magic wand.

And if you lock it down and then change your mind? To allow the PF to enable VFs again, just call xe_sriov_pf_end_lockdown. We love a reversible glow-up 💅

🔥 RETURN 🔥

  • 0 on success — slay, it worked 💖
  • a negative error code on failure — not the vibe, check your code 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/xe/xe_sriov_pf.c — plus these iconic siblings (iykyk):

💀 reminder bestie: PF only. If VFs are already on, you're getting -EBUSY and that's just the rules.

and that's the whole page 🎀 this came straight out of ./drivers/gpu/drm/xe, dated October 2026, and the page itself is xe_sriov_pf_lockdown(9) — mwah, go lock down that PF 💜✨

📦 where this page comes from