STRUCT SEV_DATA_SEND_FINISH(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ‘‘ struct sev_data_send_finish(9) β€” the Kernel API Manual moment

okay so bestie, welcome to the struct sev_data_send_finish(9) page πŸ’– this is a Kernel API Manual entry, and honestly? it's short, it's sweet, it's giving minimalist icon energy. no cap, sometimes a struct just has one job and does it flawlessly ✨


🌸 NAME 🌸

struct sev_data_send_finish β€” literally the parameter bundle for the SEND_FINISH command πŸŽ€ that's it, that's the whole vibe.


πŸ¦‹ SYNOPSIS πŸ¦‹

struct sev_data_send_finish {
    u32 handle;
 };

look at her. one member. immaculate. πŸ’…


πŸ’œ Members πŸ’œ

  • handle β€” the handle of the VM to process 🫢 like, which VM are we finishing the send for? this field knows. it's the main character of the entire struct, lowkey by default since she's the only one 😭

⭐ SEE ALSO ⭐

okay this is the part where the page goes absolutely feral with cross-references β€” like a group chat where everyone's @-ing everyone πŸ”₯ but fr fr, they're all real and here's every single one, no skips, no cuts:

  • 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_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_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)

like. that's the whole friend group 😭 and yes, the kernel file it all lives in is ./include/linux/psp-sev.h β€” that's the address, iykyk 🧚


ngl bestie, this struct has exactly one field and zero drama. but that one u32 handle is doing the lord's work for the SEND_FINISH command, so show some respect πŸ’€βœ¨

and that's the page!! this little gem lives at ./include/linux, dated October 2026, and it's filed under struct sev_data_send_finish(9) β€” slay, periodt, hope this helped bestie πŸŽ€πŸ’–πŸ¦‹

πŸ“¦ where this page comes from