libnvme_mi_aem_enable(9)

💖 libnvme_mi_aem_enable — like, the AE-enabling era 💖

okay bestie, welcome to the libnvme API manual (that's the whole flex, we're in the big leagues now) and this page is all about libnvme_mi_aem_enable. yes it's a mouthful. no we don't make the rules. let's get into it 🫶

---

✨ NAME ✨

libnvme_mi_aem_enable — Enable AE on the provided endpoint. that's it. that's the whole vibe check 👑

---

🌸 SYNOPSIS 🌸

int libnvme_mi_aem_enable (struct libnvme_mi_ep *ep , struct
       libnvme_mi_aem_config *config , void *userdata );

exactly like that, spacing and all, don't come for me 💅

---

🎀 ARGUMENTS 🎀

• ep — Endpoint to enable AEs. this is the main character of the whole operation ✨
• config — AE configuraiton including which events are enabled and the callback function. so it's like the settings page and the contact list, lowkey doing two jobs 🔥
• userdata — Application provided context pointer for callback function. your little bag of stuff that gets handed back to you later, no cap 🎒

---

🦋 DESCRIPTION 🦋

so this function is called to enable AE on the endpoint. like, that's its whole purpose, it's very focused, we respect it.

once it's in there, the Endpoint will provide the initial state (if any) of enabled AEs, and your application can parse those via the aem_handler fn pointer in callbacks. Thes — yes, that's a real word in the original, it's giving typo but we move 😭 — can be obtained in the callback by calling libnvme_mi_aem_get_next_event. get it? the events are waiting for you inside the callback. iconic 💜

so next up: the Application should poll the fd that can be obtained from libnvme_mi_aem_get_fd, and then call libnvme_mi_aem_process when poll indicates data available. poll first, process after. order matters, bestie, don't skip steps 🙈

and a call to libnvme_mi_aem_process will grab AEM data and call the aem_handler fn pointer. at this point the application can call libnvme_mi_aem_get_next_event to get information for each triggered event. so the flow goes: poll → process → get_next_event, one event at a time, slay 🌈

fr fr, this is the whole cycle — libnvme_mi_aem_get_fd for the fd, poll it, libnvme_mi_aem_process when there's data, then libnvme_mi_aem_get_next_event from inside your callback to walk the triggered events. that's the loop, no cap.

---

⭐ RETURN ⭐

0 on success, negative error code otherwise. classic. very "you'll know" of it 💀

---

and that's the page!! mwah 💋

this lil masterpiece is from the libnvme API manual, dated October 2026, and it's literally the libnvme_mi_aem_enable entry of that very manual — same name up top, same name at the bottom, the full circle moment 🎀✨