From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] Activate Virtualization On Demand v2 Date: Tue, 16 Jun 2009 17:02:00 +0300 Message-ID: <4A37A5D8.6090504@redhat.com> References: <1245065405-5714-1-git-send-email-agraf@suse.de> <20090615121737.GA11510@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Graf , kvm@vger.kernel.org To: Christoph Hellwig Return-path: Received: from mx2.redhat.com ([66.187.237.31]:56792 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751505AbZFPOB6 (ORCPT ); Tue, 16 Jun 2009 10:01:58 -0400 In-Reply-To: <20090615121737.GA11510@infradead.org> Sender: kvm-owner@vger.kernel.org List-ID: On 06/15/2009 03:17 PM, Christoph Hellwig wrote: > On Mon, Jun 15, 2009 at 01:30:05PM +0200, Alexander Graf wrote: > >> X86 CPUs need to have some magic happening to enable the virtualization >> extensions on them. This magic can result in unpleasant results for >> users, like blocking other VMMs from working (vmx) or using invalid TLB >> entries (svm). >> >> Currently KVM activates virtualization when the respective kernel module >> is loaded. This blocks us from autoloading KVM modules without breaking >> other VMMs. >> > > That will only become interesting if we every have such a thing in > mainline. So NACK, lots of complication for no good reason. > If it were truly lots of complication, I might agree. But it isn't, and we keep getting reports from users about it. -- error compiling committee.c: too many arguments to function