ixgbevf_hv_c..._mac_link_vf(9)

📦 version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the <pink>ixgbevf_hv_c..._mac_link_vf(9)</pink> page, the Hyper-V flavored corner of the kernel API docs 🎀 pull up a chair, this one's short and sweet ngl.

✨ NAME ✨

ixgbevf_hv_check_mac_link_vf — literally just checks the link, that's the whole vibe 💖

🌸 SYNOPSIS 🌸

s32 ixgbevf_hv_check_mac_link_vf (struct ixgbe_hw *hw , ixgbe_link_speed
*speed , bool *link_up , bool autoneg_wait_to_complete );

it's giving "returns an s32, takes four args" — no cap, that's the whole signature 🦋

🎀 ARGUMENTS 🎀

  • hw — pointer to the private hardware struct, the main character of every ixgbevf function fr 💅
  • speed — pointer to the link speed, so it can write the answer back out
  • link_up — true if the link is up, false otherwise 🫶
  • autoneg_wait_to_complete — unused 😭 yep, it's just... there. sitting pretty. doing nothing.

💜 DESCRIPTION 💜

so this is the Hyper-V variant of the link check, and the key detail — the thing you gotta remember for the exam — is that there's no mailbox communication. none. zero. not a single mailbox message. it's a Hyper-V thing, that's the whole point, iykyk 🔥

🌈 SEE ALSO 🌈

  • the kernel file itself: ./drivers/net/ethernet/intel/ixgbevf/vf.c ⭐

and the whole friend group, in order, all of them:

like, all 28 of them, no crumbs left behind 🙈

heads up bestie: this page came out of ./drivers/net/ethernet/intel/i... and it's dated October 2026 📅 that's the source and the date, and the manual name is ixgbevf_hv_c..._mac_link_vf(9) in case you forgot already 💀 anyway ily, go check that link 🧚💜
📦 where this page comes from