On 04/01/19 16:50, Sean Christopherson wrote:
> Tangentially related, does mmu_lock actually need to be held while we
> walk dirty_bitmap in kvm_{clear,get}_dirty_log_protect()? The bitmap
> itself is protected by slots_lock (a lockdep assertion would be nice
> too), e.g. can we grab the lock iff
On Fri, Jan 04, 2019 at 07:50:36AM -0800, Sean Christopherson wrote:
> On Fri, Jan 04, 2019 at 04:54:01PM +0800, lantianyu1...@gmail.com wrote:
> > From: Lan Tianyu
> >
> > The dirty bits have already been checked in the previous check of
> > "dirty_bitmap" and mask must be non-zero value at
On Fri, Jan 04, 2019 at 04:54:01PM +0800, lantianyu1...@gmail.com wrote:
> From: Lan Tianyu
>
> The dirty bits have already been checked in the previous check of
> "dirty_bitmap" and mask must be non-zero value at this point.
>
> Signed-off-by: Lan Tianyu
> ---
> virt/kvm/kvm_main.c | 8
From: Lan Tianyu
The dirty bits have already been checked in the previous check of
"dirty_bitmap" and mask must be non-zero value at this point.
Signed-off-by: Lan Tianyu
---
virt/kvm/kvm_main.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/virt/kvm/kvm_main.c
