diff options
author | 2025-02-26 17:25:41 -0800 | |
---|---|---|
committer | 2025-03-03 07:34:56 -0800 | |
commit | 4e96f010afb2815e33c9b15a695e0e0b4cb3cea6 (patch) | |
tree | 69ff599c324a514369698df6cc0ab9306daa65bd /scripts/lib/kdoc/kdoc_files.py | |
parent | KVM: SVM: Use guard(mutex) to simplify SNP vCPU state updates (diff) | |
download | linux-rng-4e96f010afb2815e33c9b15a695e0e0b4cb3cea6.tar.xz linux-rng-4e96f010afb2815e33c9b15a695e0e0b4cb3cea6.zip |
KVM: SVM: Invalidate "next" SNP VMSA GPA even on failure
When processing an SNP AP Creation event, invalidate the "next" VMSA GPA
even if acquiring the page/pfn for the new VMSA fails. In practice, the
next GPA will never be used regardless of whether or not its invalidated,
as the entire flow is guarded by snp_ap_waiting_for_reset, and said guard
and snp_vmsa_gpa are always written as a pair. But that's really hard to
see in the code.
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
Link: https://lore.kernel.org/r/20250227012541.3234589-11-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions