NVME_MI_ADMIN_GET_LOG_TELEMETRY_HOST(2)

💖 nvme_mi_admin_get_log_telemetry_host 💖

okay bestie, welcome to the libnvme API manual ✨ this one lives in section 2 (that's the library calls girlies, not the shell commands) and it's giving "grab me that telemetry log over NVMe-MI" energy. let's get into it 🦋

---

✨ NAME ✨

nvme_mi_admin_get_log_telemetry_host — Get Telemetry Host-Initiated log page 🎀

---

🌸 SYNOPSIS 🌸

int nvme_mi_admin_get_log_telemetry_host (nvme_mi_ctrl_t ctrl , __u64 offset , __u32 len , void *log );

---

💅 ARGUMENTS 💅

• ctrl — the Controller you wanna query, like your main character of the moment 👑
• offset — Offset into the telemetry data, aka how far in you're diving 🏊‍♀️
• len — Length of provided user buffer to hold the log data, in bytes. this is your buffer's whole personality, size-wise 📏
• log — User address for log page data, the lil spot where the goods get dropped off 🎁

---

🌈 DESCRIPTION 🌈

So basically it retrieves the Telemetry Host-Initiated log page at the requested offset, using the previously existing capture. lowkey it's just going back for the data that's already been captured, not making a fresh one — fr fr, "previously existing" is the whole vibe here 💖

---

⭐ RETURN ⭐

It gives you the nvme command status if a response was received (peep enum nvme_status_field for the deets) or -1 with errno set otherwise. so if you get -1, check your errno bestie, it's telling you what went wrong 😭

no cap, always peek the return value. the status and the errno are not the same thing and the manpage said what it said 💀

---

okay that's the whole thing, you ate it 🫶 libnvme API manual, section 2, dated July 2026 — mwah, go query something iconic 💜✨