linux-kernel - Re: [PATCH 1/2] KVM: VMX: Notify if VMX is already in use

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4EDF86E4.3050701@redhat.com>
Date:	Wed, 07 Dec 2011 17:31:48 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Sasha Levin <levinsasha928@...il.com>
CC:	linux-kernel@...r.kernel.org, Joerg Roedel <joerg.roedel@....com>,
	Marcelo Tosatti <mtosatti@...hat.com>, kvm@...r.kernel.org
Subject: Re: [PATCH 1/2] KVM: VMX: Notify if VMX is already in use

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/