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: <48E1A199.8010906@zytor.com>
Date:	Mon, 29 Sep 2008 20:48:41 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Nakajima, Jun" <jun.nakajima@...el.com>
CC:	"akataria@...are.com" <akataria@...are.com>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	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>,
	"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:
>>>
>> OK, if so we should write up a formal proposal.
> 
> I assume that the scope is limited to virtualization of Linux.
> 

That's part of the problem -- it's not, and it can't be.  It's about the 
hypervisor providing a specific service to its guest, and although we 
can explain how Linux would use this, there is going to be an 
expectation -- especially for Microsoft and Apple -- that other OSes 
would use the same interfaces (to the extent they care, obviously.)

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