NVME_MI_ADMIN_GET_LOG_MI_CMD_SUPPORTED_EFFECTS(2)

✨ NAME ✨

nvme_mi_admin_get_log_mi_cmd_supported_effects — bestie, this one displays the MI Commands Supported by the controller 💖

This page lives in the libnvme API manual, so if you're the kind of girlie who reads manpages for fun (valid), you're in exactly the right place 🎀

---

🌸 SYNOPSIS 🌸

int nvme_mi_admin_get_log_mi_cmd_supported_effects (nvme_mi_ctrl_t ctrl
, bool rae , struct nvme_mi_cmd_supported_effects_log *log );

okay so it's giving function signature, it's giving three args, and it's giving int return. She's not complicated, she just wants to know things 👑

---

🦋 ARGUMENTS 🦋

• ctrl — the Controller to query 🫶 like, this is the one you're asking. the main character. the source of all the tea.
• rae — Retain asynchronous events ✨ a little bool that says whether you're holding onto those async events or not, iykyk.
• log — the MI Command Supported and Effects data structure 💅 this is where the answer gets written, bestie. it's a struct nvme_mi_cmd_supported_effects_log *, so yes, pointer, because we're fancy like that.

---

💀 RETURN 💀

So here's the tea on what comes back:

• if a response was received, you get the nvme command status — check enum nvme_status_field for what that actually means 👑
• otherwise? it's -1, and errno gets set. not the fun outcome, but at least she tells you why 😭

⚠️ fr fr, the -1 case means no response came through — always peek at errno before you start spiralling ✨

---

libnvme API manual · July 2026 — that's the source, that's the version, that's the date, and that's the whole page bestie 💖 no cap, every flag preserved, every struct intact, we ate and left no crumbs 🍓🧚⭐