diff options
| author | Sean Christopherson <[email protected]> | 2025-02-27 01:25:41 +0000 |
|---|---|---|
| committer | Sean Christopherson <[email protected]> | 2025-03-03 15:34:56 +0000 |
| commit | 4e96f010afb2815e33c9b15a695e0e0b4cb3cea6 (patch) | |
| tree | 69ff599c324a514369698df6cc0ab9306daa65bd /tools/testing/selftests/net/lib/py/utils.py | |
| parent | KVM: SVM: Use guard(mutex) to simplify SNP vCPU state updates (diff) | |
| download | kernel-4e96f010afb2815e33c9b15a695e0e0b4cb3cea6.tar.gz kernel-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 <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/utils.py')
0 files changed, 0 insertions, 0 deletions