nvme_mi_mi_..._status_poll(2)

💖 NAME 💖

nvme_mi_mi_subsystem_health_status_poll — bestie, this is the one that reads the Subsystem Health Data Structure straight out of the NVM subsystem. Like a lil wellness check for your drive, no cap 🩺✨

This page lives in the libnvme API manual, and it's section 2 of that manual — so when you see nvme_mi_mi_..._status_poll(2) floating around, that's just us 💅

---

✨ SYNOPSIS ✨

int nvme_mi_mi_subsystem_health_status_poll (nvme_mi_ep_t ep , bool
clear , struct nvme_mi_nvm_ss_health_status *nshds );

---

🫶 ARGUMENTS 🫶

• ep — the endpoint for MI communication. this is your lil phone line to the drive 📞
• clear — a flag that says "pls clear the Composite Controller Status state". yes queen, wipe it 🌸
• nshds — the subsystem health status data you want populated. she gets filled in 💖

---

🦋 DESCRIPTION 🦋

So basically it retrieves the Subsystem Health Data Structure into nshds. That's the whole main character moment right there.

If clear is set, it requests that the Composite Controller Status bits get cleared after the read — like, read it first, then tidy up, periodt. ✨

For the nitty-gritty on the CCS bits, go peek at NVMe-MI section 5.6. It's giving "required reading" 📚

Also see struct nvme_mi_nvm_ss_health_status — that's the whole vibe of what nshds points at 🩵

---

🎀 RETURN 🎀

It hands you back the nvme command status if a response was received (check enum nvme_status_field for the deets) or -1 with errno set otherwise. So if you get a -1, that's not a slay, that's a errno situation 😭🙈

---

no cap: this function is literally just "tell me how the subsystem's doing, and optionally clean the status bits after." iconic behavior only 💅

---

and that's the whole page, bestie!! 🧚 this lil masterpiece is part of the libnvme API manual, dated July 2026 🌈 ty for reading, go read your drive's health, mwah 💜👑