STRUCT SEV_DATA_SNP_VERIFY_MITIGATION(9)
β¨ struct sev_data_snp_verify_mitigation(9) β¨
okay so bestie, welcome to the Kernel API Manual π
and lemme tell you, this page is literally all about struct sev_data_snp_verify_mitigation β the struct that carries the params for the SNP_VERIFY_MITIGATION command. she's giving very specific, very secure, very SNP energy π
π NAME π
struct sev_data_snp_verify_mitigation β the SNP_VERIFY_MITIGATION command params π
Like, that's her whole job. she holds the command params. no cap.
πΈ SYNOPSIS πΈ
struct sev_data_snp_verify_mitigation {
u32 length;
u16 subcommand;
u16 rsvd;
u64 vector;
u32 dst_paddr_en : 1, src_paddr_en : 1, rsvd1 : 30;
u8 rsvd2[4];
u64 src_paddr;
u64 dst_paddr;
u8 rsvd3[24];
};
lowkey beautiful. bitfields and everything πβ¨
π¦ Members π¦
lengthβ the length of the command buffer that the PSP reads, periodt. πsubcommandβ the mitigation sub-command that the firmware is supposed to execute. here's the tea π:REQ_STATUS: 0x0β request status about the mitigations that are currently supported and verifiedREQ_VERIFY: 0x1β request to initiate a verification mitigation operation on one specific mitigation
rsvdβ reserved πvectorβ the bit that specifies which vulnerability mitigation to process π―dst_paddr_enβ destination paddr enabled βsrc_paddr_enβ source paddr enabled βrsvd1β reserved πrsvd2β reserved πsrc_paddrβ the source address for optional input data π₯dst_paddrβ the destination address to write the result π€rsvd3β reserved π
ngl bestie, there are a lot of reserved fields here. do not touch them. they are not for you. they are reserved. respect the rsvd π
π§ SEE ALSO π§
Kernel file ./include/linux/psp-sev.h β and like, the entire sev squad, fr fr:
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_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)sev_platform_init_args(9)struct sev_data_snp_commit(9)struct sev_data_snp_feature_info(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, the whole friend group showed up to the party π«Άβ¨
and that's the page!! mwah π this one's from ./include/linux, dated October 2026 β so like, go forth and verify those mitigations, bestie. you got this ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms