linux-kernel - Re: Use CPUID to communicate with the 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: <48E1437D.7080606@zytor.com>
Date:	Mon, 29 Sep 2008 14:07:09 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Nakajima, Jun" <jun.nakajima@...el.com>
CC:	"akataria@...are.com" <akataria@...are.com>,
	Gerd Hoffmann <kraxel@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	"avi@...hat.com" <avi@...hat.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Zach Amsden <zach@...are.com>, Daniel Hecht <dhecht@...are.com>
Subject: Re: Use CPUID to communicate with the hypervisor.

Nakajima, Jun wrote:
> 
> For example, we can set the following ranges so that so that each VMM vender can define and implement features avoiding conflicts:
> vmware to define 0x4000001X
> xen to define 0x4000002X
> kvm to define 0x4000003X
> ...
> 

Unless there is a central authority assigning these, "we" can do all we 
want, enough people will not pay attention.

Basically, there needs to be a standards document that describes the 
architecture, *and* needs to either have universal buy-in with all the 
vendors or imposed by an authority with enough clout to do so (Intel might.)

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