From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 9/24] Implement VMCLEAR Date: Thu, 05 Aug 2010 15:13:00 +0300 Message-ID: <4C5AAACC.7040400@redhat.com> References: <1276431753-nyh@il.ibm.com> <201006131227.o5DCRAB0012968@rice.haifa.ibm.com> <20100615134753.GX21797@redhat.com> <4C17852B.5080703@redhat.com> <20100615135405.GY21797@redhat.com> <20100805115025.GC16722@fermat.math.technion.ac.il> <20100805115304.GL10499@redhat.com> <20100805120136.GD16722@fermat.math.technion.ac.il> <4C5AA911.4040405@redhat.com> <20100805121027.GE16722@fermat.math.technion.ac.il> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Gleb Natapov , kvm@vger.kernel.org To: "Nadav Har'El" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:37060 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933193Ab0HEMNG (ORCPT ); Thu, 5 Aug 2010 08:13:06 -0400 In-Reply-To: <20100805121027.GE16722@fermat.math.technion.ac.il> Sender: kvm-owner@vger.kernel.org List-ID: On 08/05/2010 03:10 PM, Nadav Har'El wrote: > On Thu, Aug 05, 2010, Avi Kivity wrote about "Re: [PATCH 9/24] Implement VMCLEAR": >> As far as the processor is concerned, there is no end to physical >> memory. The VMCLEAR will write some stuff out, and the chipset will >> throw it away. > So isn't what you're saying that for accurate VMCLEAR emulation, I should > simply ignore this error and have VMCLEAR do nothing in this case? > That would be most accurate. >> However, eventually the guest will crash and burn, >> better to take it out in a controlled way. > Isn't it concievable that some poorly-written hypervisor actually VMCLEARs > something beyond available memory, and doesn't crash because it never tries > to actually use that memory later? It's very unlikely. > Do you think it's a good idea to kill > the guest immediately, in anticipation of a crash that will most likely come > later? At this stage, the problem is likely to be in the nvmx implementation. So it's best to report the problem as early as possible. -- error compiling committee.c: too many arguments to function