LIBNVME_MI_MI_SUBSYSTEM_HEALTH_STATUS_POLL-LIBNVME3(2)

💖 libnvme_mi_mi_subsystem_health_status_poll(9) 💖

okay so this is a page straight out of the libnvme API manual (yes, the whole libnvme thing, hi bestie 🫶) and it's literally all about reading the Subsystem Health Data Structure out of an NVM subsystem. very main character of it.

---

✨ SYNOPSIS ✨

int libnvme_mi_mi_subsystem_health_status_poll (struct libnvme_mi_ep *ep
, bool clear , struct nvme_mi_nvm_ss_health_status *nshds );

like, that's the whole vibe check right there 💅

---

🎀 ARGUMENTS 🎀

• ep — the endpoint you're using for MI communication. it's giving "the phone you're calling from" 📞
• clear — a flag that clears the Composite Controller Status state. yes queen, wipe it
• nshds — the subsystem health status data you want populated. this is the lil container that gets filled up 🌸

---

🦋 DESCRIPTION 🦋

so what does it do? it retrieves the Subsystem Health Data Structure and drops it into nshds. simple as that, no cap.

and if clear is set, it requests that the Composite Controller Status bits get cleared after the read. so read first, then yeet the bits. 🧹

for the deets on the CCS bits, the original is like "go read NVMe-MI section 5.6" — so like, section 5.6, that's the assignment, iykyk 📚

also!! go look at struct nvme_mi_nvm_ss_health_status, it's literally right there and it's iconic.

---

⭐ RETURN ⭐

you get the nvme command status if a response came back (peep enum nvme_status_field for that one) — or a negative error code if it didn't. so like, either it worked or it didn't, and the negative error code is the "we don't talk about it" moment 😭

lowkey important: a response being received is what gets you the command status. no response = negative error code, periodt.

---

and that's the whole page bestie, you ate that 💜✨

big sign-off energy: this cutie lives in the libnvme API manual under the name libnvme_mi_mi_subsystem_health_status_poll, and it's dated October 2026 🎀 go be great with your subsystem health data 🦋