NVME_MI_ADMIN_GET_LOG_TELEMETRY_CTRL(2)

✨ NAME ✨

nvme_mi_admin_get_log_telemetry_ctrl — the one that gets you the Telemetry Controller-Initiated log page 🦋

okay so real quick, bestie — this lives in the libnvme API manual, and it's literally your girl for pulling the controller-initiated telemetry log. periodt.

---

🌸 SYNOPSIS 🌸

int nvme_mi_admin_get_log_telemetry_ctrl (nvme_mi_ctrl_t ctrl , bool rae
, __u64 offset , __u32 len , void *log );

no cap, that's the whole vibe — five args and a dream 💅

---

🎀 ARGUMENTS 🎀

• ctrl — the Controller you're querying, aka the main character you're asking about 👑
• rae — Retain asynchronous events. yes, say it with me: retain async events ✨
• offset — how far into the telemetry data you're reaching 🫶
• len — the length of the user buffer you're providing to hold the log data, in bytes 📏
• log — the user address where the log page data goes 🏠

---

💖 DESCRIPTION 💖

So this one retrieves the Telemetry Controller-Initiated log page at the requested offset — using the previously existing capture. not a fresh new one, the one that's already there. iykyk 😌

---

🔥 RETURN 🔥

It hands you back the nvme command status if a response was received — go peek at enum nvme_status_field for the deets — or -1 with errno set otherwise. so either you get the tea ☕ or you get an errno. no in-between, fr fr.

lowkey important: if you get the -1, that's not a shrug, that's <errno> telling you what went wrong. respect the errno bestie 💀

---

and that's the whole page, you ate that 🌈 stay iconic, go query ur controller, mwah 💜

✨ July 2026 · libnvme API manual · nvme_mi_admin_get_log_telemetry_ctrl(2) ✨