NVME_MI_ADMIN_GET_LOG_PHY_RX_EOM(2)

✨ nvme_mi_admin_get_log_phy_rx_eom ✨

okay bestie, welcome to the libnvme API manual 💖 you're about to learn how to pull a whole Physical Interface Receiver Eye Opening Measurement Log and honestly? iconic behavior.

🌸 NAME 🌸

nvme_mi_admin_get_log_phy_rx_eom — Retrieve Physical Interface Receiver Eye Opening Measurement Log

no cap, that's the whole vibe: it fetches that log for you 🫶

---

🦋 SYNOPSIS 🦋

int nvme_mi_admin_get_log_phy_rx_eom (nvme_mi_ctrl_t ctrl , __u8 lsp ,
__u16 controller , __u32 len , struct nvme_phy_rx_eom_log *log );

she takes five things and gives you back an int, that's the whole deal 💅

---

🎀 ARGUMENTS 🎀

• ctrl — the Controller you wanna query. that's your main character ✨
• lsp — "Log specific", which controls the action and the measurement quality. so she's the one calling the shots on how the measurement goes down 🔥
• controller — the Target controller ID. yep, aimed at a specific controller, not just vibes 🎯
• len — the allocated size, minimum struct nvme_phy_rx_eom_log. so like, don't skimp on the buffer, give her at least that much room 🙈
• log — the user address to store the log page. this is where the good stuff lands 📥

---

💜 RETURN 💜

so what do you get back? The nvme command status if a response was received (see enum nvme_status_field) — or -1 with errno set otherwise. that's it, that's the tea 🍓

lowkey important: if you get a status back, check enum nvme_status_field for the deets. if you get -1, the errno is where the drama lives 💀

---

and that's the whole page, periodt 👑

mwah 💋 this came from the libnvme API manual, dated July 2026 — go slay some log retrieval bestie, ily 🧚💖