From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 1/2] KVM: VMX: Notify if VMX is already in use Date: Wed, 07 Dec 2011 17:31:48 +0200 Message-ID: <4EDF86E4.3050701@redhat.com> References: <1322764218-4698-1-git-send-email-levinsasha928@gmail.com> <4EDF7590.5060701@redhat.com> <1323267521.4009.11.camel@lappy> <4EDF76D6.7020800@redhat.com> <1323267891.4009.16.camel@lappy> <4EDF7797.9080103@redhat.com> <1323270953.4009.21.camel@lappy> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, Joerg Roedel , Marcelo Tosatti , kvm@vger.kernel.org To: Sasha Levin Return-path: In-Reply-To: <1323270953.4009.21.camel@lappy> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 12/07/2011 05:15 PM, Sasha Levin wrote: > > Ah, maybe they do it differently on AMD. Or they changed things. > > I've grabbed their code just to see whats going on there and traced the > vmxon calls back to module init. > > Are you sure it ever happened on-demand and not on init? If you are, > I'll actually build that module and give it a go :) I'm pretty sure, but they likely changed things. vmxon/off all the time is not very performant. -- error compiling committee.c: too many arguments to function