STRUCT SEV_DATA_DEACTIVATE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct sev_data_deactivate(9) β€” from the Kernel API Manual, bestie

okay so real talk: this is the manual page for struct sev_data_deactivate, and it's literally the official Kernel API Manual entry for it. it's short. it's snappy. it's giving "one job and she does it." let's go ✨


🌸 NAME 🌸

struct sev_data_deactivate β€” the DEACTIVATE command parameters, periodt. that's it, that's the whole vibe. this struct is where the DEACTIVATE command keeps its parameters, and we love a focused queen πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

here's the whole entire struct, no cap. one field. iconic:

struct sev_data_deactivate {
    u32 handle;
 };

like… she's minimal. she's main character energy with exactly one u32 in her bag πŸ’…


πŸ‘‘ Members πŸ‘‘

  • handle β€” the handle of the VM you wanna deactivate. that's the whole field, bestie. that's the one thing you put in there 🫢

πŸ”₯ SEE ALSO πŸ”₯

okay so this is the part where the page goes absolutely feral and name-drops the entire friend group. no skips, no cuts β€” every single one of these is in the original so every single one is here πŸ’–

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

and now, the squad, in the exact order they showed up:

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

and that's the whole page, bestie β€” short, sweet, and fully cross-referenced 🧚

fr fr this one is so small you could read it in the time it takes to send a text. don't overthink it πŸ’€

sign-off szn πŸŽ€ β†’ this page lives under ./include/linux, it's dated October 2026, and the manual name is struct sev_data_deactivate(9). now go deactivate that VM, you absolute icon πŸ‘‘βœ¨

πŸ“¦ where this page comes from