STRUCT SEV_DATA_DBG(9)

💅 struct sev_data_dbg(9) — a Kernel API Manual moment

okay bestie, so this little icon is from the Kernel API Manual (the 9 girlies, you know the ones), and she's here to explain struct sev_data_dbg — literally the parameters for the DBG_ENCRYPT/DBG_DECRYPT command. no cap, that's the whole gig. 🎀

---

✨ NAME ✨

struct sev_data_dbg — the parameters for the DBG_ENCRYPT/DBG_DECRYPT command. that's it, that's her whole personality 🦋

---

🌸 SYNOPSIS 🌸

struct sev_data_dbg {
    u32 handle;
    u32 reserved;
    u64 src_addr;
    u64 dst_addr;
    u32 len;
 };

she's giving very structured, very demure, five fields and not one of them is extra. ✨

---

🎀 Members 🎀

okay so let's meet the cast, one by one, main character energy each:

• handle — the handle of the VM that's gonna do the debug operation. like her little ID badge 💳
• src_addr — the source address of the data we're operating on. where the data's coming from, bestie 📤
• dst_addr — the destination address of the data we're operating on. where it's going 📥
• len — the len of data to operate on. yes it's literally called len, she's not trying to be mysterious 🫶

ngl the struct also has a reserved field up top — the manpage doesn't give it its own member blurb, so we're just gonna wave at it politely from across the room and not make stuff up about it. 🙈

---

👑 SEE ALSO 👑

literally the whole extended friend group, no one's getting left out of this group chat 💖

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

then, deep breath, in order:

• 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_update_vmsa(9)
• struct sev_data_receive_finish(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 squad, and yes i listed every single one because we don't do "etc." in this house 💅

---

and that's the page, bestie! this masterpiece lives in ./include/linux, dated October 2026, and answers to the name struct sev_data_dbg(9). go forth and debug, you absolute icon 🌈👑💜