NVME_INIT_GET_LOG_FDP_EVENTS-LIBNVME3(2)

💖 nvme_init_get_log_fdp_events — a libnvme API manual moment 💖

okay bestie, so like, this is a section 9 page from the libnvme API manual and the function is nvme_init_get_log_fdp_events — yes the actual page header truncates it to nvme_init_ge...g_fdp_events(9) which honestly is giving "my name is too long for the terminal" energy 😭 but we move.

---

🌸 NAME 🌸

nvme_init_get_log_fdp_events — Initialize passthru command for Flexible Data Placement Events. like that's literally the whole vibe, she sets up the passthru command so you can go get those FDP events 🔥

---

✨ SYNOPSIS ✨

void nvme_init_get_log_fdp_events (struct libnvme_passthru_cmd *cmd ,
bool host_events , __u16 egid , __u64 lpo , void *log , __u32 len );

no return value, she's a void, she just does her thing and leaves 💅

---

🎀 ARGUMENTS 🎀

• cmd — the passthru command you're gonna use. this is the lil container she's filling up 🫶
• host_events — a bool that decides whose events you're reporting: host or controller. pick a side, bestie.
• egid — Endurance group identifier, a __u16. iykyk 🧚
• lpo — offset into the log page, a __u64. that's where we start reading, no cap.
• log — the log page data buffer (void *), the actual destination for all that data 📥
• len — length, in bytes, of the user buffer you provided to hold the log data. keep it exact or things get weird 💀

---

💜 DESCRIPTION 💜

So what she actually does: she initializes the passthru command buffer for the Get Log command with LID value NVME_LOG_LID_FDP_EVENTS. that's it, that's the whole job, and she does it immaculately 👑

ngl the LID constant is the main character here — NVME_LOG_LID_FDP_EVENTS — literally the key to the whole thing 🔑

---

k bye bestie, go log some events 🦋

✨ sign-off time ✨ this page comes from the libnvme API manual, dated October 2026, and its source/footer line is the very same nvme_init_ge...g_fdp_events(9) situation as the top — so yeah, we came full circle 💖🎀💅