ice_trigger_vf_reset(9)

💅 ice_trigger_vf_reset(9) — like, the kernel API manual page, bestie 🎀

okay so you found the page for ice_trigger_vf_reset in the kernel API manual and honestly? iconic of you. let's get into it ✨

---

✨ NAME ✨

ice_trigger_vf_reset — Reset a VF on HW 🫶

---

🌸 SYNOPSIS 🌸

void ice_trigger_vf_reset (struct ice_vf *vf , bool is_vflr , bool
is_pfr );

like, it returns void, it takes three things, no cap 💅

---

🦋 ARGUMENTS 🦋

• vf — pointer to the VF structure. it's giving "the actual star of the show" 👑
• is_vflr — true if VFLR was issued, false if not. yes literally just those two vibes 🍓
• is_pfr — true if the reset was triggered due to a previous PFR. (note: it says true if, it does not say what false means, and I'm not out here inventing facts for you 🙈)

---

🔥 DESCRIPTION 🔥

Trigger hardware to start a reset for a particular VF. that's the whole mission, bestie. 💀

lowkey the important part: it expects the caller to wait the proper amount of time to allow hardware to reset the VF before it cleans up and restores VF functionality. so like… this function does the triggering, you do the waiting. don't leave the hardware hanging, it's rude 😭

fr fr — if you skip the waiting part, the cleanup-and-restore step has no business happening yet. the manpage says "expects the caller to wait", so be the caller who waits. 🫶

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/net/ethernet/intel/ice/ice_vf_lib.c

and then the whole friend group, in this exact order because we respect the list 🧚:

ice_get_vf_by_id(9), ice_release_vf(9), ice_put_vf(9), ice_has_vfs(9), ice_get_num_vfs(9), ice_get_vf_vsi(9), ice_is_vf_disabled(9), ice_wait_on_vf_reset(9), ice_check_vf_ready_for_cfg(9), ice_vf_pre_vsi_rebuild(9), ice_vf_reconfig_vsi(9), ice_vf_rebuild_vsi(9), ice_vf_rebuild_host_vlan_cfg(9), ice_vf_rebuild_host_tx_rate_cfg(9), ice_vf_set_host_trust_cfg(9), ice_vf_rebuild_host_mac_cfg(9), ice_vf_rebuild_aggregator_node_cfg(9), ice_vf_rebuild_host_cfg(9), ice_set_vf_state_qs_dis(9), ice_vf_set_initialized(9), ice_vf_post_vsi_rebuild(9), ice_is_any_vf_in_unicast_promisc(9), ice_vf_get_promisc_masks(9), ice_vf_clear_all_promisc_modes(9), ice_vf_set_vsi_promisc(9), ice_vf_clear_vsi_promisc(9), ice_reset_vf_mbx_cnt(9), ice_reset_all_vfs(9), ice_notify_vf_reset(9), ice_reset_interrupts(9), ice_reset_vf(9), ice_set_vf_state_dis(9), ice_initialize_vf_entry(9), ice_dis_vf_qs(9), ice_err_to_virt_err(9), ice_check_vf_init(9), ice_vf_get_port_info(9), ice_cfg_mac_antispoof(9), ice_vsi_ena_spoofchk(9), ice_vsi_dis_spoofchk(9), ice_vsi_apply_spoofchk(9), ice_is_vf_trusted(9), ice_vf_has_no_qs_ena(9), ice_is_vf_link_up(9), ice_vf_ctrl_invalidate_vsi(9), ice_vf_ctrl_vsi_release(9), ice_vf_ctrl_vsi_setup(9), ice_vf_init_host_cfg(9), ice_vf_invalidate_vsi(9), ice_vf_vsi_release(9), ice_get_vf_ctrl_vsi(9), ice_vf_update_mac_lldp_num(9)

like, that's the whole squad, and yes you should probably read ice_wait_on_vf_reset(9) next, iykyk 👀

---

anyway that's the page!! go wait the proper amount of time and slay 💜

source/version: ./drivers/net/ethernet/intel/ice — dated October 2026, mwah 💋