STRUCT SEV_DATA_ACTIVATE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct sev_data_activate(9) β€” the Kernel API Manual moment

okay so bestie, welcome to the struct sev_data_activate(9) page πŸ’– this one lives in the Kernel API Manual and it's literally the whole vibe check for the ACTIVATE command parameters. tiny struct, big main character energy. let's get into it ✨


🌸 NAME

struct sev_data_activate β€” the parameters for the ACTIVATE command πŸŽ€ that's it, that's the whole job, and she does it flawlessly.


✨ SYNOPSIS

struct sev_data_activate {
    u32 handle;
    u32 asid;
 };

two u32s and a dream, no cap 🫢 look at her. iconic.


πŸ¦‹ Members

  • handle β€” the handle of the VM you're activating πŸ”₯ literally whose VM is this, that's the whole thing.
  • asid β€” the asid that got assigned to the VM πŸ’« the ID she's gonna be known by, iykyk.
ngl there are only two members and i'm obsessed with the efficiency πŸ’… no notes.

πŸ‘‘ SEE ALSO

okay so the family tree is huge and we're not skipping a single relative, periodt 🩷 also peep the kernel file ./include/linux/psp-sev.h β€” that's where she lives, bestie 🌈

  • 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_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_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 squad πŸ’œ read them, love them, cite them in your commit message fr fr.


and that's the page, bestie πŸŽ€ this lil gem comes from ./include/linux, dated October 2026, filed under struct sev_data_activate(9) β€” go activate something slay πŸ’…βœ¨πŸŒΈ

πŸ“¦ where this page comes from