Messages in this thread | | | Subject | Re: [PATCH 16/18] KVM: Don't take mmu_lock for range invalidation unless necessary | From | Paolo Bonzini <> | Date | Wed, 31 Mar 2021 23:00:19 +0200 |
| |
On 31/03/21 22:52, Sean Christopherson wrote: > 100% agree with introducing on_lock separately from the conditional locking. > > Not so sure about introducing conditional locking and then converting non-x86 > archs. I'd prefer to keep the conditional locking after arch conversion. > If something does go awry, it would be nice to be able to preciesly bisect to > the conditional locking. Ditto if it needs to be reverted because it breaks an > arch.
Ok, that sounds good too.
Paolo
| |