NVME_INIT_GET_LOG_TELEMETRY_CTRL-LIBNVME3(2)

💅 nvme_init_get_log_telemetry_ctrl(9) — libnvme API manual 💅

okay bestie, welcome to the libnvme API manual, page nine of the function section, and lemme tell you this one is short but it matters 🫶

---

✨ NAME ✨

nvme_init_get_log_telemetry_ctrl — bestie's little helper that initializes the passthru command for Telemetry Controller-Initiated. yes that whole mouthful. she does exactly one thing and she does it flawlessly 👑

---

🌸 SYNOPSIS 🌸

void nvme_init_get_log_telemetry_ctrl (struct libnvme_passthru_cmd *cmd
, __u64 lpo , void *log , __u32 len );

it's void, she returns nothing, she just sets things up and vibes. no cap 💅

---

🦋 ARGUMENTS 🦋

• cmd — the passthru command you're gonna use. this is the main character right here 👑 you hand her over and she gets filled in (respectfully).
• lpo — offset into the telemetry data. like, where in the telemetry data are we even looking 🧚 type __u64, she's fancy like that.
• log — the user address for the log page data. this is where the good stuff lands 🍓
• len — length of the provided user buffer that holds the log data, in bytes (yes, bytes, not vibes, keep it exact bestie 😭)

---

🔥 DESCRIPTION 🔥

so what does she actually do? she initializes the passthru command buffer for the Get Log command, with the LID value set to NVME_LOG_LID_TELEMETRY_CTRL. that's it. that's the whole flex ✨

like, no extra steps, no secret sauce, just a clean passthru command buffer with the right LID value so the Telemetry Controller-Initiated log request actually goes through. iconic behavior honestly 🌈

💀 heads up: she only fills in the command buffer. the actual cmd you pass in is yours to manage, so don't come for her if your buffer's a mess 🙈

---

🎀 sign-off 🎀

and that's the whole page bestie, we ate and left no crumbs 🔥 this little beauty is from the libnvme API manual, dated October 2026 — go forth, init those telemetry ctrl passthru commands, and slay ⭐💜