Andi Kleen wrote:
But at least for Linux, if we notify the
guest telling it to retune (which can include the vsyscall path) we can
avoid the cost entirely.
Hmm, we discussed something like this some time ago anyways (add
a way to rescan CPUID features) because there are microcode updates
around that change some (relatively obscure) CPUID features.
But doing it fully general would be likely quite intrusive. You
would need to rewrite the CPU initialization code and some other
code in a callback like matter like the PCI code does for hotplug.
The primary consumer would be compat mode syscall/sysenter. Page copy
would be a secondary consumer. All the rest are likely in the noise.
Hmm, maybe also the raid5+ algorithms.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
