This is mostly useful for userspace that doesn't disable the quirk, right?Isn't this the opposite? If I understand the original proposal correctly,
the reason that we include the TSC_ADJUST in the new ioctl, is that
we would like to disable the special kvm behavior (that is disable the quirk),
which would mean that tsc will jump on regular host initiated TSC_ADJUST write.
To avoid this, userspace would set TSC_ADJUST through this new interface.
Do you think that this is an issue? If so I can make the code work with
signed numbers.
About nsec == 0, this is to allow to use this API for VM initialization.
(That is to call KVM_SET_TSC_PRECISE prior to doing KVM_GET_TSC_PRECISE)