xe_configfs_get_max_vfs(9)

💖 xe_configfs_get_max_vfs(9) 💖

okay so bestie, welcome to the Kernel API Manual — yes we're reading kernel docs together, this is our bonding time now 🫶

---

✨ NAME ✨

xe_configfs_get_max_vfs — literally just get the number of VFs that could be managed 👑

---

🌸 SYNOPSIS 🌸

unsigned int xe_configfs_get_max_vfs (struct pci_dev *pdev );

---

🎀 ARGUMENTS 🎀

• pdev — the pci_dev device, aka the main character of this whole function 💅

---

🦋 DESCRIPTION 🦋

So here's the vibe: it goes and finds the configfs group that belongs to the PCI device, and then it hands you back the maximum number of Virtual Functions (VFs) that could be managed by this device ✨

And if that configfs group is just… not present? not invited to the party? 🙈 then it lowkey falls back to using the value of the max_vfs module parameter. no group, no problem, we improvise 💁‍♀️

---

⭐ RETURN ⭐

The maximum number of VFs that could be managed. that's it, that's the answer, periodt 💖

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/gpu/drm/xe/xe_configfs.c — Xe Configfs(9)
• xe_configfs_check_device(9)
• xe_configfs_get_survivability_mode(9)
• xe_configfs_primary_gt_allowed(9)
• xe_configfs_media_gt_allowed(9)
• xe_configfs_get_engines_allowed(9)
• xe_configfs_get_psmi_enabled(9)
• xe_configfs_get_enable_multi_queue(9)
• xe_configfs_get_ctx_restore_mid_bb(9)
• xe_configfs_get_ctx_restore_post_bb(9)
• xe_configfs_admin_only_pf(9)

like yes that's a whole friend group of functions, they all run together, iykyk 🌈

---

and that's a wrap bestie!! 🎀 this came outta ./drivers/gpu/drm/xe back in October 2026, filed under xe_configfs_get_max_vfs(9) — mwah, go read some kernel source, it's giving main character energy 👑💜