xe_sriov_pf_assert_vfid(9)

💅 xe_sriov_pf_assert_vfid(9) 💅

okay so this is a page from the Kernel API Manual, and honestly? it's a little vibe-check function for driver devs 🫶

---

✨ NAME ✨

xe_sriov_pf_assert_vfid — bestie, this one just warns you if &id isn't a supported VF number, but only when you're debugging 💖

---

🌸 SYNOPSIS 🌸

xe_sriov_pf_assert_vfid (xe , vfid );

that's the whole thing, no cap. two args, in and out, done ✨

---

🎀 ARGUMENTS 🎀

• xe — the PF xe_device you're asserting on. like, the actual physical function device, the main character 👑
• vfid — the VF number you wanna assert. the number under scrutiny, fr fr 🔍

---

🦋 DESCRIPTION 🦋

okay so here's the tea 🍓: this asserts that xe actually represents the Physical Function (PF) device, and that the vfid you handed it is inside the range of supported VF numbers. that range goes up to the max number of VFs the driver can support — and yes, that includes VF0, which represents the PF itself 💅 lowkey important detail, don't forget it.

so it's checking two things at once: right device, right number. iconic behavior, honestly 🌈

---

⭐ NOTE ⭐

heads up bestie 😭 this is effective only on debug builds. so if you're on a non-debug build, don't expect it to do anything — it's giving "not me showing up to the party that isn't happening" 💀

for the full deets, see Xe Asserts_ 💜

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/gpu/drm/xe/xe_sriov_pf_helpers.h — the source of truth, go read it 🧚
• xe_sriov_pf_get_totalvfs(9) — the total VFs one
• xe_sriov_pf_num_vfs(9) — the num VFs one
• xe_sriov_pf_admin_only(9) — the admin only one

the whole friend group, slay 👑

---

aaaand that's the page!! 🎀 byeee, this one lives in ./drivers/gpu/drm/xe, dated October 2026 — so like, future vibes only 🦋✨💖