Move the call to kvm_mmu_flush_or_zap outside the loop.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/mmu.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 725316df32ec..6d47b5c43246 100644
--- a/arch/x86/kvm/mmu.c
+++ b/
On 2016/02/24 22:17, Paolo Bonzini wrote:
> Move the call to kvm_mmu_flush_or_zap outside the loop.
>
> Signed-off-by: Paolo Bonzini
> ---
> arch/x86/kvm/mmu.c | 9 ++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index 725
On 02/25/2016 10:15 AM, Takuya Yoshikawa wrote:
On 2016/02/24 22:17, Paolo Bonzini wrote:
Move the call to kvm_mmu_flush_or_zap outside the loop.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/mmu.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kvm
On 25/02/2016 03:15, Takuya Yoshikawa wrote:
> On 2016/02/24 22:17, Paolo Bonzini wrote:
>> Move the call to kvm_mmu_flush_or_zap outside the loop.
>>
>> Signed-off-by: Paolo Bonzini
>> ---
>> arch/x86/kvm/mmu.c | 9 ++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --gi
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
On 02/25/2016 04:49 PM, Paolo Bonzini wrote:
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
On 25/02/2016 10:10, Xiao Guangrong wrote:
>
>
> On 02/25/2016 04:49 PM, Paolo Bonzini wrote:
>>
>>
>> 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
7 matches
Mail list logo