qed_iov_is_valid_vfid(9)

💖 qed_iov_is_valid_vfid(9) 💖

okay so this is from the Kernel API Manual, and it's literally the VF ID validity-checking bestie you didn't know you needed. no cap, it's giving "small function, big gatekeeping energy" 👑

---

✨ NAME ✨

qed_iov_is_valid_vfid — check if the given VF ID @vfid is valid w.r.t. @b_enabled_only.

So the tea is: if b_enabled_only = true, only an enabled VF id is valid. otherwise, any VF id less than max_vfs is valid. that's the rule, periodt 💅

---

🦋 SYNOPSIS 🦋

bool qed_iov_is_valid_vfid (struct qed_hwfn *p_hwfn , int rel_vf_id , bool b_enabled_only , bool b_non_malicious );

---

🌸 ARGUMENTS 🌸

• p_hwfn — HW device data. the hardware main-character struct, iykyk 🫶
• rel_vf_id — Relative VF ID. literally the VF id we're checking, bestie.
• b_enabled_only — consider only enabled VF. so if this is on, enabled-only is the vibe check.
• b_non_malicious — true iff we want to validate vf isn't malicious. not me doing a lil security side-eye 🙈

---

🔥 RETURN 🔥

bool — true for valid VF ID. that's it, that's the answer, slay ✨

---

🎀 SEE ALSO 🎀

Kernel file ./drivers/net/ethernet/qlogic/qed/qed_sriov.h — go read it, bestie, it's right there 👑

• qed_iov_get_next_active_vf(9)
• qed_iov_hw_info(9)
• qed_add_tlv(9)
• qed_dp_tlv_list(9)
• qed_sriov_vfpf_malicious(9)
• qed_sriov_eqe_event(9)
• qed_iov_alloc(9)
• qed_iov_setup(9)
• qed_iov_free(9)
• qed_iov_free_hw_info(9)
• qed_iov_mark_vf_flr(9)
• qed_iov_search_list_tlvs(9)

---

made with 💖 from ./drivers/net/ethernet/qlogic/qed, dated October 2026 🎀