This is great, obviously... although we'll have to deal with legacy
methods for a while if not indefinitely (just as we have to for
pre-CPUID processors).
Ok, do you think we should keep those (legacy) interfaces separate so
that they can be phased out whenever the time is right.
I would like to see this as a generic hypervisor way to get frequency
rather than a VMware specific thingy.In order for *that* to be safe, you'd have to have well-defined ranges
for different virtualization vendors where each of them can define their
own stuff.
My motivation for doing this is to have a standard across all the
hypervisor's. If all the different hypervisor guys can come to some
sought of consensus on the various hypervisor leafs that would help keep
this simple and a lot more maintainable.