On Tue, Dec 03, 2024 at 02:30:44PM +0530, Nikunj A Dadhania wrote:
> SecureTSC enabled guests should use TSC as the only clock source, terminate
> the guest with appropriate code when clock source switches to hypervisor
> controlled kvmclock.
This looks silly. Why not prevent kvm_register_clock() from succeeding simply
on a secure-TSC guest?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
