Alok Kataria wrote:
quoted text
> 
> How does that matter, if we are able to standardize all this then,
> hypervisors which want to run a Linux guest should effectively play by
> the standards over here or else they would never work properly on Linux.
> What we are trying to do here is try to standardize things for Linux so
> that the Linux kernel implementation for Virtualization is that much
> more easier. If this goes well other closed source hypervisors too can
> effectively follow these standards. 
> If the other closed source hypervisors define their own cpuid leafs they
> will still have to make Linux kernel side changes to make use of these
> new leafs. Which allows them to add to these pool of cpuid interface's
> too.
> 

I don't think this is a realistic point of view, especically given who 
we're dealing with in the closed-source world.

Without any kind of tagging of the information, it's realistically futile.

Intel/AMD haven't helped any by reserving a space which is entirely too 
small.

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