nvme_get_log_phy_rx_eom(2)

💖 nvme_get_log_phy_rx_eom — NAME 💖

okay bestie, presenting: nvme_get_log_phy_rx_eom — she retrieves the Physical Interface Receiver Eye Opening Measurement Log 👁️✨

this is a page from the libnvme API manual (yes, section 2, we're fancy like that) 💅

---

🌸 SYNOPSIS 🌸

int nvme_get_log_phy_rx_eom (int fd , __u8 lsp , __u16 controller ,
       __u32 len , struct nvme_phy_rx_eom_log *log );

like… five args, no notes, copy it exactly how it is, don't be cute with it 😭

---

🎀 ARGUMENTS 🎀

• fd — the file descriptor of your nvme device 🫶 like, the actual door you're knocking on
• lsp — log specific, which controls the action and the measurement quality ✨ (yes it does two jobs, she's versatile)
• controller — the target controller ID 🎯 the one specific controller you're asking about
• len — the allocated size, and the minimum is struct nvme_phy_rx_eom_log 📏 so don't come in under that, bestie
• log — user address to store the log page 🏠 that's where the good stuff gets written

---

🔥 RETURN 🔥

so here's the tea: you get the nvme command status if a response was received — see enum nvme_status_field for all the deets 👑

and if not?? you get -1 with errno set otherwise 💀 no cap, that's the whole deal.

lowkey important: check errno when you see that -1, she's not going to explain herself otherwise 🙈

---

and that's the vibe check, we're done here 💜

this whole thing is the libnvme API manual, from nvme_get_log_phy_rx_eom(2), dated July 2026 🦋 mwah, go get those eye opening measurements, you got this 🎀✨🌈