STRUCT SEV_DATA_RECEIVE_UPDATE_VMSA(9)

🎀 struct sev_data_receive_update_vmsa 🎀

okay so bestie, this is the Kernel API Manual page for struct sev_data_receive_update_vmsa — the parameter struct for the RECEIVE_UPDATE_VMSA command. It’s giving “one neat little packet of fields” energy, and honestly? iconic. ✨

✨ NAME ✨

struct sev_data_receive_update_vmsa — the parameters for the RECEIVE_UPDATE_VMSA command. 💅

🧚 SYNOPSIS 🧚

Here’s the struct layout from the page, no cap:

struct sev_data_receive_update_vmsa {
    u32 handle;
    u32 reserved1;
    u64 hdr_address;
    u32 hdr_len;
    u32 reserved2;
    u64 guest_address;
    u32 guest_len;
    u32 reserved3;
    u64 trans_address;
    u32 trans_len;
};

🌸 Members 🌸

The page spells out these member descriptions. And yes, reserved1, reserved2, and reserved3 are sitting up in the layout too, but the manual doesn’t give them their own little blurbs. Okay? Okay. 🫶

• handle — the handle of the VM that’s getting updated. 👑
• hdr_address — the physical address that holds the packet header blob. ✨
• hdr_len — the length of that packet header. 📏
• guest_address — the system physical address of the guest memory region. 💖
• guest_len — the length of the guest memory region. 🌸
• trans_address — the system physical address of the transport buffer. 🦋
• trans_len — the length of the transport buffer. 🎀

💖 SEE ALSO 💖

Kernel file: ./include/linux/psp-sev.h.

Go peek at these besties:

• struct sev_data_init(9)
• struct sev_data_init_ex(9)
• struct sev_data_pek_csr(9)
• struct sev_data_download_firmware(9)
• struct sev_data_get_id(9)
• struct sev_data_pdh_cert_export(9)
• struct sev_data_decommission(9)
• struct sev_data_activate(9)
• struct sev_data_deactivate(9)
• struct sev_data_guest_status(9)
• struct sev_data_launch_start(9)
• struct sev_data_launch_update_data(9)
• struct sev_data_launch_update_vmsa(9)
• struct sev_data_launch_measure(9)
• struct sev_data_launch_secret(9)
• struct sev_data_launch_finish(9)
• struct sev_data_send_start(9)
• struct sev_data_send_finish(9)
• struct sev_data_send_cancel(9)
• struct sev_data_receive_start(9)
• struct sev_data_receive_update_data(9)
• struct sev_data_receive_finish(9)
• struct sev_data_dbg(9)
• struct sev_data_attestation_report(9)
• struct sev_data_snp_download_firmware(9)
• struct sev_data_snp_activate(9)
• struct sev_data_snp_addr(9)
• struct sev_data_snp_launch_start(9)
• struct sev_data_snp_launch_update(9)
• struct sev_data_snp_launch_finish(9)
• struct sev_data_snp_guest_status(9)
• struct sev_data_snp_page_reclaim(9)
• struct sev_data_snp_page_unsmash(9)
• struct sev_data_snp_dbg(9)
• struct sev_data_snp_guest_request(9)
• struct sev_data_snp_init_ex(9)
• struct sev_data_range(9)
• struct sev_data_range_list(9)
• struct sev_data_snp_shutdown_ex(9)
• struct sev_platform_init_args(9)
• struct sev_data_snp_commit(9)
• struct sev_data_snp_feature_info(9)
• struct sev_data_snp_verify_mitigation(9)
• struct sev_data_snp_verify_mitigation_dst(9)
• struct sev_snp_tcb_version_genoa_milan(9)
• struct sev_snp_tcb_version_turin(9)
• sev_module_init(9)
• sev_platform_init(9)
• sev_platform_status(9)
• sev_issue_cmd_external_user(9)
• sev_guest_deactivate(9)
• sev_guest_activate(9)
• sev_guest_df_flush(9)
• sev_guest_decommission(9)
• sev_do_cmd(9)

that’s the whole vibe check, bestie 🫶 This page came from ./include/linux, dated October 2026, and the footer tag is struct sev_..._update_vmsa(9). Periodt. 💅✨