From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrea Arcangeli Subject: Re: [PATCH 4/6] kvm-userland.git mmu notifier compat Date: Tue, 29 Jul 2008 15:03:35 +0200 Message-ID: <20080729130335.GM11494@duo.random> References: <20080725142452.GA8217@duo.random> <20080725142639.GB8217@duo.random> <20080725143203.GC8217@duo.random> <20080725143834.GD8217@duo.random> <488F11C4.5050109@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Marcelo Tosatti , kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from host36-195-149-62.serverdedicati.aruba.it ([62.149.195.36]:44325 "EHLO mx.cpushare.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753300AbYG2NDk (ORCPT ); Tue, 29 Jul 2008 09:03:40 -0400 Content-Disposition: inline In-Reply-To: <488F11C4.5050109@qumranet.com> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Jul 29, 2008 at 03:49:08PM +0300, Avi Kivity wrote: > Applied; thanks. I think page pinning can be worked around by pinning all > pages on memslot registration (and unpinning on memslot removal); this will > slow down virtual machine startup, but is at least simple. This has the benefit that will also fix the tlb issues, but if we go this way if a sles/rhel user takes the next kvm release, all ram will be pinned and it won't swap anything for him, like with my patch that added VM_LOCKED. Said that swap wasn't a reliable feature before so nobody should have depended on that. If we really go this memslot-wide-pinning way I could submit to rhel and sles a mmu notifier backport so the rhel/sles users won't have to wait to get their kernel upgraded to 2.6.27 to get full kvm-paging.