lkml.org 
[lkml]   [2021]   [Mar]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 16/18] KVM: Don't take mmu_lock for range invalidation unless necessary
From
Date
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

\
 
 \ /
  Last update: 2021-03-31 23:01    [W:0.286 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site