STRUCT SVSM_VTPM_CMD_RESPONSE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

okay so bestie, welcome to the manual page for struct svsm_vtpm_cmd_response β€” it's the struct you get back for a TPM_SEND_COMMAND response. that's it, that's the vibe. it's the lil' container that holds whatever the TPM sent back to you 🫢

(this whole page lives under struct svsm...cmd_response(9) in the Kernel API Manual, iykyk ✨)


πŸ¦‹ SYNOPSIS πŸ¦‹

struct svsm_vtpm_cmd_response {
    u32 buf_size;
    u8 buf[];
 };

like, literally two members. tiny struct, main character energy πŸ‘‘


πŸŽ€ Members πŸŽ€

  • buf_size β€” the size of the output buffer that follows. it's the u32 that tells you how much buffer is actually behind the curtain πŸ“
  • buf β€” a buffer of size buf_size. the actual payload lives here, and its size is, surprise, buf_size πŸ’€

🌸 Description 🌸

so this struct is defined by the AMD SVSM spec [1] β€” specifically in the section called "8.2 SVSM_VTPM_CMD Call", Table 17: TPM_SEND_COMMAND Response Structure. and here's how that table lays out, no cap:

  • Byte Offset 0x000 β€” Size (Bytes) 4 β€” Meaning: response size (in bytes) ✨
  • Byte Offset 0x004 β€” Size (Bytes) Variable β€” Meaning: response πŸ’–

so yeah, the first 4 bytes tell you how big the response is, and then the response itself is variable-length right after. it's giving "header then payload", and honestly? obsessed 🌈


πŸ’œ SEE ALSO πŸ’œ


anyway bestie that's the whole page, mwah πŸ’‹ β€” this one's from ./include/linux, dated October 2026, and it signs off as struct svsm...cmd_response(9). slay, go read those TPM structs, periodt πŸ”₯πŸ‘‘

πŸ“¦ where this page comes from