From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] KVM on VMI Date: Thu, 10 Jul 2008 16:55:06 +0300 Message-ID: <487614BA.6030600@qumranet.com> References: <48746F83.2020702@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Alexander Graf Return-path: Received: from il.qumranet.com ([212.179.150.194]:20229 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754981AbYGJNzH (ORCPT ); Thu, 10 Jul 2008 09:55:07 -0400 In-Reply-To: <48746F83.2020702@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: Alexander Graf wrote: > Hi, > > I more or less accidently stumbled across a problem when compiling KVM > on the VMI-enabled kernel. Even though that's pretty much useless > right now, I think there might be a day, VMware will emulate VM > extensions, in VMs, so we should probably not keep KVM from running > under VMI. > > The problem is that usually load_ldt is #defined, while in VMI it's a > static void function. This clashes with the way KVM detects if > load_ldt is defined already. To circumvent this, I just extended the > check so we're not redefining load_ldt when VMI is activated. > I fixed this in another way, by renaming prefixing load_ldt (and a bunch of other functions) with kvm_. -- error compiling committee.c: too many arguments to function