diff options
author | Sean Christopherson <seanjc@google.com> | 2025-02-27 04:25:39 +0300 |
---|---|---|
committer | Sean Christopherson <seanjc@google.com> | 2025-03-03 18:34:54 +0300 |
commit | e268beee4a25ce58807a96253e95e96c2e3a5c1a (patch) | |
tree | b32996b449cc418794b628e6faed80348be0b799 /tools/perf/scripts/python/task-analyzer.py | |
parent | 46332437e1c546e2ade4fedab2715c66bce573cc (diff) | |
download | linux-e268beee4a25ce58807a96253e95e96c2e3a5c1a.tar.xz |
KVM: SVM: Mark VMCB dirty before processing incoming snp_vmsa_gpa
Mark the VMCB dirty, i.e. zero control.clean, prior to handling the new
VMSA. Nothing in the VALID_PAGE() case touches control.clean, and
isolating the VALID_PAGE() code will allow simplifying the overall logic.
Note, the VMCB probably doesn't need to be marked dirty when the VMSA is
invalid, as KVM will disallow running the vCPU in such a state. But it
also doesn't hurt anything.
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
Link: https://lore.kernel.org/r/20250227012541.3234589-9-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions