[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56CEC003.1070402@redhat.com>
Date: Thu, 25 Feb 2016 09:49:07 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Xiao Guangrong <guangrong.xiao@...ux.intel.com>,
Takuya Yoshikawa <yoshikawa_takuya_b1@....ntt.co.jp>,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Cc: mtosatti@...hat.com
Subject: Re: [PATCH 09/12] KVM: MMU: coalesce zapping page after
mmu_sync_children
On 25/02/2016 08:35, Xiao Guangrong wrote:
>> This may release the mmu_lock before committing the zapping.
>> Is it safe? If so, we may want to see the reason in the changelog.
>
> It is unsafe indeed, please do not do it.
Can you explain why? kvm_zap_obsolete_pages does the same.
Paolo
Powered by blists - more mailing lists