diff options
author | 2023-03-21 15:00:11 -0700 | |
---|---|---|
committer | 2023-04-04 12:37:30 -0700 | |
commit | 697c89bed94effde145d84e618142dd89b2b54af (patch) | |
tree | 651b62af4618d6b9550a3b09ca70e0ed825f4c1a /scripts/generate_rust_analyzer.py | |
parent | KVM: x86/mmu: Use kvm_ad_enabled() to determine if TDP MMU SPTEs need wrprot (diff) | |
download | wireguard-linux-697c89bed94effde145d84e618142dd89b2b54af.tar.xz wireguard-linux-697c89bed94effde145d84e618142dd89b2b54af.zip |
KVM: x86/mmu: Consolidate Dirty vs. Writable clearing logic in TDP MMU
Deduplicate the guts of the TDP MMU's clearing of dirty status by
snapshotting whether to check+clear the Dirty bit vs. the Writable bit,
which is the only difference between the two flavors of dirty tracking.
Note, kvm_ad_enabled() is just a wrapper for shadow_accessed_mask, i.e.
is constant after kvm-{intel,amd}.ko is loaded.
Link: https://lore.kernel.org/all/Yz4Qi7cn7TWTWQjj@google.com
Signed-off-by: Vipin Sharma <vipinsh@google.com>
[sean: split to separate patch, apply to dirty log, write changelog]
Link: https://lore.kernel.org/r/20230321220021.2119033-4-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions