Re: [PATCH 2/3] X86: Add a check to catch Xen emulation of Hyper-V

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/31/2013 08:45 AM, Jan Beulich wrote:
On 31.01.13 at 16:53, KY Srinivasan <kys@xxxxxxxxxxxxx> wrote:
Are there any published standards in terms of how the CPUID space should be
populated in the range from 0x40000000 to 0x40010000. Specifically, unless

I recall having seen this range being marked as reserved for
hypervisor use somewhere, but I don't remember where that was.


AFAIK Intel reserves 0x40000000 to 0x4FFFFFFF for hypervisor use. Typically multivendor CPUID utilities expect "blocks" of 64K but that is not in any spec that I know of.

	-hpa

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

_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel


[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux