Re: [PATCH 2/2] KVM: x86: Optimize mmio spte zapping when creating/moving memslot

2013-03-12 Thread Marcelo Tosatti
On Tue, Mar 12, 2013 at 02:06:22PM +0200, Gleb Natapov wrote: > On Tue, Mar 12, 2013 at 05:45:30PM +0900, Takuya Yoshikawa wrote: > > When we create or move a memory slot, we need to zap mmio sptes. > > Currently, zap_all() is used for this and this is causing two problems: > > - extra page faults

Re: [PATCH 2/2] KVM: x86: Optimize mmio spte zapping when creating/moving memslot

2013-03-12 Thread Gleb Natapov
On Tue, Mar 12, 2013 at 05:45:30PM +0900, Takuya Yoshikawa wrote: > When we create or move a memory slot, we need to zap mmio sptes. > Currently, zap_all() is used for this and this is causing two problems: > - extra page faults after zapping mmu pages > - long mmu_lock hold time during zapping m

[PATCH 2/2] KVM: x86: Optimize mmio spte zapping when creating/moving memslot

2013-03-12 Thread Takuya Yoshikawa
When we create or move a memory slot, we need to zap mmio sptes. Currently, zap_all() is used for this and this is causing two problems: - extra page faults after zapping mmu pages - long mmu_lock hold time during zapping mmu pages For the latter, Marcelo reported a disastrous mmu_lock hold time