nvme_init_g..._config_list(9)

💅 nvme_init_get_log_support_cap_config_list — libnvme API manual

okay bestie, buckle up, because this one is a mouthful of a function name and i need you to say it with your whole chest. it lives in the libnvme API manual and it's genuinely so much simpler than it looks, i promise 🫶

---

✨ NAME ✨

nvme_init_get_log_support_cap_config_list — literally just initializes the passthru command for the Supported Capacity Configuration List. that's it. that's the whole vibe. 🎀

---

🌸 SYNOPSIS 🌸

void nvme_init_get_log_support_cap_config_list (struct
libnvme_passthru_cmd *cmd , __u16 domid , struct
nvme_supported_cap_config_list_log *cap );

she returns void, so no "did it work?" moment — she just does the thing and moves on, main character energy fr 💅

---

🦋 ARGUMENTS 🦋

• cmd — the passthru command you're gonna use. hand her the buffer, she fills it in. simple as that ✨
• domid — Domain Identifier selection, if supported. it's a __u16, so be normal about it 🙈
• cap — the user address where the supported capabilities config list gets stored. point her at your spot and she'll drop the goods there 🍓

---

👑 DESCRIPTION 👑

so what does she actually do? she initializes the passthru command buffer for the Get Log command, with the LID value set to:

NVME_LOG_LID_SUPPORTED_CAP_CONFIG_LIST

that's the whole description. no hidden lore, no secret caveats, no "undefined behaviour if you sneeze" warnings — just vibes and a log ID. iconic of her honestly 🌈

ngl this is one of those functions where the name is 10x scarier than the function. you're literally just prepping a buffer. slay 💀✨

---

💖 a lil sign-off 💖

that's the whole page, bestie! this gem comes to you from the libnvme API manual, dated October 2026 — so yes, she's from the future and she's still just initializing passthru buffers. some things never change 😭🫶

go forth and initialize ✨🧚‍♀️💜