nvme_mi_adm...ost_discover(2)

✨ NAME ✨

nvme_mi_admin_get_log_host_discover — bestie, this is the one that goes and Retrieves the Host Discovery Log 💖 (and yeah, it's a libnvme API manual situation, so come sit with me)

---

🦋 SYNOPSIS 🦋

int nvme_mi_admin_get_log_host_discover (nvme_mi_ctrl_t ctrl , bool
allhoste , bool rae , __u32 len , struct nvme_host_discover_log *log );

okay so it's giving "one function, four-ish arguments, whole lotta lore" 😭

---

🌸 ARGUMENTS 🌸

• ctrl — the Controller to query, like the main character you're walking up to and asking for the tea 🫶
• allhoste — All host entries. yes bestie, that's the actual spelling, it is what it is 💅
• rae — Retain asynchronous events. not me keeping the async events around like they're unread memes 🎀
• len — The allocated length of the log page. literally how much room you gave it to spill 🍓
• log — User address to store the log page. that's where the receipts get written down ✨

---

👑 RETURN 👑

The nvme command status if a response was received (see enum nvme_status_field) or -1 with errno set otherwise.

translation: it either hands you a status and says "yeah we heard back 🫶" or it throws a -1 at you with errno set, which is its way of being like "no response, check errno bestie" 💀

---

lowkey iconic of libnvme to ship this, fr fr no cap — July 2026 edition, from the libnvme API manual, going out to the whole group chat as nvme_mi_admin_get_log_host_dnvme_mi_adm...ost_discover(2) 🌈✨ mwah, use it responsibly, ily, bye 💜