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: <48E0A36D.1010400@redhat.com>
Date:	Mon, 29 Sep 2008 12:44:13 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Tim Deegan <Tim.Deegan@...rix.com>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>, akataria@...are.com,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Zach Amsden <zach@...are.com>,
	Daniel Hecht <dhecht@...are.com>,
	"Jun.Nakajima@...el.Com" <Jun.Nakajima@...el.Com>
Subject: Re: Use CPUID to communicate with the hypervisor.

Tim Deegan wrote:
> I was talking about checking every 256 leaves from 0x40000000, but I
> can't remember where I heard it.  The only relevant reference I can
> find is the MS hypervisor interface spec's description of leaf
> 0x40000001: "Hypervisor vendor-neutral interface identification.  This
> determines the semantics of the leaves from 0x40000002 through
> 0x400000FF"
>
>   

This was discussed at the virtualization mini summit (can't remember who 
brought it up).

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

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