diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2021-08-03 03:45:41 -0400 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2021-08-03 03:54:08 -0400 |
| commit | 071064f14d87536e38235df1bdeabe404023203f (patch) | |
| tree | be48cfdff46fbaedb60513a0049d1b49f2c328ce /crypto | |
| parent | 52ac8b358b0cb7e91c966225fca61be5d1c984bc (diff) | |
| download | linux-071064f14d87536e38235df1bdeabe404023203f.tar.gz linux-071064f14d87536e38235df1bdeabe404023203f.tar.bz2 linux-071064f14d87536e38235df1bdeabe404023203f.zip | |
KVM: Don't take mmu_lock for range invalidation unless necessary
Avoid taking mmu_lock for .invalidate_range_{start,end}() notifications
that are unrelated to KVM. This is possible now that memslot updates are
blocked from range_start() to range_end(); that ensures that lock elision
happens in both or none, and therefore that mmu_notifier_count updates
(which must occur while holding mmu_lock for write) are always paired
across start->end.
Based on patches originally written by Ben Gardon.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions