svsm_vtpm_cmd_request_fill(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– svsm_vtpm_cmd_request_fill(9) β€” the "pack your TPM command into a request" girlie ✨

Okay bestie, gather round, because this is one of those little kernel helpers from the Kernel API Manual that does exactly one job and does it slayfully πŸ’…. svsm_vtpm_cmd_request_fill takes your raw TPM command bytes and packages them up into a TMP_SEND_COMMAND request so it can be sent off to SVSM. That's it. That's the whole vibe check. πŸŽ€


🌸 NAME 🌸

svsm_vtpm_cmd_request_fill β€” fill a TMP_SEND_COMMAND request to be sent to SVSM ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

int svsm_vtpm_cmd_request_fill (struct svsm_vtpm_cmd_request *req , u8
locality , const u8 *buf , size_t len );

Lowkey just four args and a return value, and she ate. πŸ”₯


πŸ‘‘ ARGUMENTS πŸ‘‘

  • req β€” the struct svsm_vtpm_cmd_request you want filled, bestie. This is the blank canvas, the empty fit that's about to get styled. 🫢
  • locality β€” the locality. Yep, that's the whole description, an u8, no cap. It's the locality, okay? 😭
  • buf β€” the buffer where the payload of the command gets copied from. It's const, so hands off, we're only reading. πŸ™ˆ
  • len β€” the size of the buffer. It's a size_t, so be normal about it. ✨

⭐ RETURN ⭐

  • 0 on success β€” slay, it worked, main character energy πŸŽ‰
  • a negative error code on failure β€” not slay, something went sideways, check the errno vibe πŸ’€

🌈 SEE ALSO 🌈

Kernel file ./include/linux/tpm_svsm.h and its whole friend group:

  • struct svsm_vtpm_request(9)
  • struct svsm_vtpm_response(9)
  • struct svsm_vtpm_cmd_request(9)
  • struct svsm_vtpm_cmd_response(9)
  • svsm_vtpm_cmd_response_parse(9)

iykyk, go read them, they're all connected 🧚


ngl this page is short but she's iconic. Every argument listed, every return value honoured, every SEE ALSO reference kept intact. Periodt. πŸ‘‘

Later, bestie β€” this one's from ./include/linux, dated October 2026, and it lives its life as page svsm_vtpm_cmd_request_fill(9). Mwah. πŸ’œ

πŸ“¦ where this page comes from