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

[H. Peter Anvin]

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/