NVME_MI_ADMIN_GET_LOG_BOOT_PARTITION(2)

πŸ’– nvme_mi_admin_get_log_boot_partition β€” it's the libnvme API manual bestie ✨

okay so. picture this: you're deep in NVMe-over-MI land πŸ¦‹, and you need the Boot Partition log page. that's it. that's the function. it's giving "let me retrieve Boot Partition for you, no cap" πŸ‘‘


🌸 NAME 🌸

nvme_mi_admin_get_log_boot_partition β€” Retrieve Boot Partition πŸ’…


✨ SYNOPSIS ✨

int nvme_mi_admin_get_log_boot_partition (nvme_mi_ctrl_t ctrl , bool rae
, __u8 lsp , __u32 len , struct nvme_boot_partition *part );

πŸŽ€ ARGUMENTS πŸŽ€

  • ctrl β€” Controller to query πŸ” like, this is the controller you're asking, she's the main character here.
  • rae β€” Retain asynchronous events ✨ (yes queen, keep those async events, do not let them go).
  • lsp β€” The log specified field of LID 🧚 literally the log specified field of LID, that's the whole vibe.
  • len β€” The allocated size, minimum struct nvme_boot_partition πŸ“ so like, allocate at least that much bestie, don't be out here with a tiny buffer.
  • part β€” User address to store the log page πŸ’Ύ your address, your storage, your log page. we're writing it right there.

🫢 RETURN 🫢

The nvme command status if a response was received (see enum nvme_status_field) β€” or -1 with errno set otherwise 😭

lowkey important: if you get a response, you get the nvme command status. if you don't, it's -1 and errno is set. that's the whole deal, fr fr πŸ’€

and that's the page!! go off, retrieve that Boot Partition, you absolute icon πŸ‘‘πŸŒˆβ­

this was the libnvme API manual, nvme_mi_admi...ot_partition(2), dated July 2026 πŸ’œ mwah, bye bestie πŸŽ€

πŸ“¦ where this page comes from