On 02/26/2010 12:46 PM, Ingo Molnar wrote:
Right, this will severely limit migration domains to hosts of the same
vendor and processor generation. There is a middle ground, though,
Intel has recently moved to define an "architectural pmu" which is not
model specific. I don't know if AMD adopted it. We could offer both
options - native host capabilities, with a loss of compatibility, and
the architectural pmu, with loss of model specific counters.
I only had a quick look yet on the architectural pmu from intel but it looks
like it can be emulated for a guest on amd using existing features.
AMD CPUs dont have enough events for that, they cannot do the 3 fixed events
in addition to the 2 generic ones.
Nor do you really want to standardize on KVM guests on returning
'GenuineIntel' in CPUID, so that the various guest side OSs use the Intel PMU
drivers, right?
No - that would only work if AMD also adopted the architectural pmu.
Note virtualization clusters are typically split into 'migration pools'
consisting of hosts with similar processor features, so that you can
expose those features and yet live migrate guests at will. It's likely
that all hosts have the same pmu anyway, so the only downside is that we
now have to expose the host's processor family and model.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
