NVME_MI_ADMIN_GET_LOG_AVE_DISCOVER(2)

✨ NAME ✨

nvme_mi_admin_get_log_ave_discover — bestie, this is the one that goes and *Retrieve*s the AVE Discovery Log 💖

It lives in the libnvme API manual, so if you're poking at NVMe-MI stuff and you need that AVE discovery log page… yeah. This is her. 👑

---

🌸 SYNOPSIS 🌸

int nvme_mi_admin_get_log_ave_discover (nvme_mi_ctrl_t ctrl , bool rae ,
       __u32 len , struct nvme_ave_discover_log *log );

no cap, that's the whole signature. four args, one int coming back at you. 🫶

---

🎀 ARGUMENTS 🎀

• ctrl — the Controller to query. this is the one you're asking, bestie, be nice to her 💅
• rae — Retain asynchronous events. it's a bool, so true/false energy only ✨
• len — The allocated length of the log page. yes, you have to pass how much room you made. it's giving "adulting" 😭
• log — User address to store the log page. hand over the pointer, she'll do the rest 🦋

---

💜 RETURN 💜

So like… what do you get back? 💫

• The nvme command status if a response was received — check enum nvme_status_field for the tea 🔍
• or -1 with errno set otherwise. if you see the -1, that's your sign to go read errno, periodt 💀

fr fr: don't just check "did it fail", check what it told you. the status is the whole plot. 📖

---

🌈 okay that's the page, bestie! the vibe check is complete and everything's still here: nvme_mi_admin_get_log_ave_discover, nvme_mi_ctrl_t ctrl, bool rae, __u32 len, struct nvme_ave_discover_log *log, the enum nvme_status_field glow-up, and the -1 + errno classic. 🫶

sign-off szn: this lil slice of libnvme API manual dropped July 2026, and the footer's whole identity is basically nvme_mi_admin_get_log_ave_discover(2) — cute, iconic, slightly unhinged header-wrapping, we love her. mwah 💋