Chris Wright wrote: > * Anthony Liguori (anthony@xxxxxxxxxxxxx) wrote: > >> And arguably, storing TSC frequency in CPUID is a terrible interface >> because the TSC frequency can change any time a guest is entered. It >> > > True for older hardware, newer hardware should fix this. I guess the > point is, the are numbers that are easy to measure incorrectly in guest. > Doesn't justify the whole thing.. > It's not fixed for newer hardware. Larger systems still have multiple tsc frequencies. -- error compiling committee.c: too many arguments to function _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization