summaryrefslogtreecommitdiffstats
path: root/block/blk-stat.c
diff options
context:
space:
mode:
authorDavid Matlack <dmatlack@google.com>2022-01-14 00:30:20 +0100
committerPaolo Bonzini <pbonzini@redhat.com>2022-01-19 18:09:07 +0100
commit6ff94f27fd47847d6ecb9302f9d3bd1ca991a17f (patch)
tree46b0b4efa5eaecca415e7a15f4f7490edc882101 /block/blk-stat.c
parentKVM: x86/mmu: Document and enforce MMU-writable and Host-writable invariants (diff)
downloadlinux-6ff94f27fd47847d6ecb9302f9d3bd1ca991a17f.tar.xz
linux-6ff94f27fd47847d6ecb9302f9d3bd1ca991a17f.zip
KVM: x86/mmu: Improve TLB flush comment in kvm_mmu_slot_remove_write_access()
Rewrite the comment in kvm_mmu_slot_remove_write_access() that explains why it is safe to flush TLBs outside of the MMU lock after write-protecting SPTEs for dirty logging. The current comment is a long run-on sentence that was difficult to understand. In addition it was specific to the shadow MMU (mentioning mmu_spte_update()) when the TDP MMU has to handle this as well. The new comment explains: - Why the TLB flush is necessary at all. - Why it is desirable to do the TLB flush outside of the MMU lock. - Why it is safe to do the TLB flush outside of the MMU lock. No functional change intended. Signed-off-by: David Matlack <dmatlack@google.com> Message-Id: <20220113233020.3986005-5-dmatlack@google.com> Reviewed-by: Sean Christopherson <seanjc@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'block/blk-stat.c')
0 files changed, 0 insertions, 0 deletions