From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC][PATCH 0/9] rework KVM mmu_shrink() code Date: Thu, 17 Jun 2010 11:40:32 +0300 Message-ID: <4C19DF80.6060909@redhat.com> References: <20100615135518.BC244431@kernel.beaverton.ibm.com> <4C188D8B.40508@redhat.com> <1276700596.6437.16867.camel@nimitz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org To: Dave Hansen Return-path: In-Reply-To: <1276700596.6437.16867.camel@nimitz> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 06/16/2010 06:03 PM, Dave Hansen wrote: > On Wed, 2010-06-16 at 11:38 +0300, Avi Kivity wrote: > >> On 06/15/2010 04:55 PM, Dave Hansen wrote: >> >>> These seem to boot and run fine. I'm running about 40 VMs at >>> once, while doing "echo 3> /proc/sys/vm/drop_caches", and >>> killing/restarting VMs constantly. >>> >>> >> Will drop_caches actually shrink the kvm caches too? If so we probably >> need to add that to autotest since it's a really good stress test for >> the mmu. >> > I'm completely sure. Yes, easily seen from the code as well. > I crashed my machines several times this way > during testing. > Hopefully only with your patches applied? I'll try to run autotest from time to time with drop_caches running in the background. Looks like an excellent way to stress out the mmu. -- error compiling committee.c: too many arguments to function