nvme_set_fe..._sw_progress(2)

πŸ’– nvme_set_features_sw_progress(2) πŸ’–

okay bestie, welcome to the libnvme API manual ✨ this one's short and sweet, we love a low-effort slay πŸŽ€


✨ NAME ✨

nvme_set_features_sw_progress β€” set the pre-boot software load count feature πŸ’…

like. that's the whole vibe. it sets a feature. the feature is about pre-boot software load count. periodt 🫢


🌸 SYNOPSIS 🌸

int nvme_set_features_sw_progress (int fd , __u8 pbslc , bool save ,
       __u32 *result );

there she is πŸ‘‘ four lil things go in, an int comes out. no cap.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • fd β€” the file descriptor of the nvme device 🧚 this is your ticket in, your main character entry pass, the thing that says "yes hello i would like to talk to this drive please"
  • pbslc β€” the Pre-boot Software Load Count ⭐ it's a __u8, so it's smol but it matters
  • save β€” a bool that says whether to save the value across power states πŸ’€ like, do you want this to survive a reboot or not, bestie, decide
  • result β€” a pointer to a __u32 where the command completion result from CQE dword0 lands 🌈 that's the drive's lil receipt for what just happened

πŸ’œ RETURN πŸ’œ

so here's the tea β˜• this returns the nvme command status if a response was received β€” peep enum nvme_status_field for all the possible moods it can come back in πŸ‘€

and if no response showed up? you get -1, with errno set instead πŸ™ˆ classic.

bestie warning: don't just check for -1 and call it a day, okay? a response did come back sometimes and it's still a status code you gotta read. the -1 path is the "nobody picked up the phone" path πŸ“ž

πŸŽ€ a lil sign-off πŸŽ€

this page lives in the libnvme API manual, and it was dated July 2026 β€” yes, future girl summer πŸ’… go forth and set your features, queen πŸ‘‘βœ¨πŸŒΈπŸ¦‹

πŸ“¦ where this page comes from