From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 16/22] KVM: MMU: Track page fault data in struct vcpu Date: Tue, 04 May 2010 12:20:02 +0300 Message-ID: <4BDFE6C2.2040601@redhat.com> References: <1272364712-17425-1-git-send-email-joerg.roedel@amd.com> <1272364712-17425-17-git-send-email-joerg.roedel@amd.com> <4BD6DF7C.1090203@redhat.com> <20100503163221.GB28950@amd.com> <4BDFD295.7000702@redhat.com> <20100504091157.GC28950@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , "kvm@vger.kernel.org" , "linux-kernel@vger.kernel.org" To: "Roedel, Joerg" Return-path: In-Reply-To: <20100504091157.GC28950@amd.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 05/04/2010 12:11 PM, Roedel, Joerg wrote: > On Tue, May 04, 2010 at 03:53:57AM -0400, Avi Kivity wrote: > >> On 05/03/2010 07:32 PM, Joerg Roedel wrote: >> >>> On Tue, Apr 27, 2010 at 03:58:36PM +0300, Avi Kivity wrote: >>> >>> >>>> So we probably need to upgrade gva_t to a u64. Please send this as >>>> a separate patch, and test on i386 hosts. >>>> >>>> >>> Are there _any_ regular tests of KVM on i386 hosts? For me this is >>> terribly broken (also after I fixed the issue which gave me a >>> VMEXIT_INVALID at the first vmrun). >>> >>> >>> >> No, apart from the poor users. I'll try to set something up using nsvm. >> > Ok. I will post an initial fix for the VMEXIT_INVALID bug soon. Apart > from that I get a lockdep warning when I try to start a guest. The guest > actually boots if it is single-vcpu. SMP guests don't even boot through > the BIOS for me. > > Strange. i386 vs x86_64 shouldn't have that much effect! -- error compiling committee.c: too many arguments to function