NVME_MI_ADMIN_GET_LOG_PERSISTENT_EVENT(2)

✨ NAME ✨

nvme_mi_admin_get_log_persistent_event β€” bestie, this is how you Retrieve Persistent Event Log πŸ’– (it lives in the libnvme API manual, section 2, if you were wondering where it hangs out)


🌸 SYNOPSIS 🌸

int nvme_mi_admin_get_log_persistent_event (nvme_mi_ctrl_t ctrl , enum
nvme_pevent_log_action action , __u32 size , void *pevent_log );

πŸŽ€ ARGUMENTS πŸŽ€

  • ctrl β€” the Controller you're querying. This is the one you're asking, okay, they're the main character here πŸ‘‘
  • action β€” the Action the controller should take while it's processing this command. Lowkey this is you telling it how to behave.
  • size β€” the Size of pevent_log. Gotta tell it how much room there is, no cap.
  • pevent_log β€” the User address to store the persistent event log. This is where the tea gets written πŸ“

πŸ’… RETURN πŸ’…

It hands you back the nvme command status if a response was received (see enum nvme_status_field) β€” or, and this is the not-so-slay part, -1 with errno set otherwise. 😭

So like, always check. A -1 means check errno, fr fr.

that's the whole page, babe, go forth and log your persistent events βœ¨πŸ¦‹

signing off from the libnvme API manual, July 2026 edition πŸ’œπŸŽ€ β€” stay iconic, drink water, and read your enum nvme_status_field like the queen you are πŸ‘‘

πŸ“¦ where this page comes from