NVME_GET_LOG_SUPPORTED_LOG_PAGES(2)

💖 NAME 💖

nvme_get_log_supported_log_pages — Retrieve nmve supported log pages

okay bestie, this is the one that goes and asks your NVMe drive "hey queen, which log pages do you even support?" and the drive answers. iconic behavior, fr fr.

---

✨ SYNOPSIS ✨

int nvme_get_log_supported_log_pages (int fd , bool rae , struct
nvme_supported_log_pages *log );

look at her. one function call. three little arguments. absolute main character energy 💅

---

🎀 ARGUMENTS 🎀

• fd — File descriptor of nvme device. this is the little handle you already opened for the drive, the group chat invite basically 🫶
• rae — Retain asynchronous events. pass this and you're telling the firmware "don't clear your async event stuff on me", no cap.
• log — Array of LID supported and Effects data structures. this is where the drive drops the receipts — all the LIDs it supports plus the Effects data. it's giving ✨output parameter✨

---

🌸 RETURN 🌸

bestie, here's the tea on what comes back:

• The nvme command status if a response was received (see enum nvme_status_field) — so like, you get the actual status back, go look it up in enum nvme_status_field iykyk.
• or -1 with errno set otherwise. yeah. the sad path. 😭 when that happens, errno is where the drama lives.

---

lowkey reminder: the error path is -1 and errno gets set — both, together. don't forget the errno bestie, it's not coming to you alone 💀

---

and that's the whole page, periodt. this was nvme_get_log_supported_log_pages(2) from the libnvme API manual, dated July 2026 🌈💜 — go slay some log pages, you got this ✨🧚