linux-kernel - Re: [PATCH -tip] x86: move vmware to hypervisor

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <49BFC6CB.9070603@zytor.com>
Date:	Tue, 17 Mar 2009 08:50:35 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jaswinder Singh Rajput <jaswinder@...nel.org>
CC:	Ingo Molnar <mingo@...e.hu>, x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>, akataria@...are.com
Subject: Re: [PATCH -tip] x86: move vmware to hypervisor

Jaswinder Singh Rajput wrote:
>> I dont really like this one. KVM is a hypervisor too, and so is 
>> Xen and lguest. VMware is one of the many types of a 
>> hypervisors.
> 
> Can we use common hypervisor for Xen, lguest, vmware, etc.
> And Xen, lguest, vmware will be the sub-options.

Obviously.  We spent a lot of time breaking up the cpu stuff into common
and vendor-specific portions, we shouldn't go backwards w.r.t. hypervisors.
	
	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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/