On Thu, Jan 02, 2025 at 03:31:49PM +0530, Nikunj A. Dadhania wrote:
> Sure, how about the below:
>
> For SecureTSC enabled guests, TSC frequency should be obtained from the platform
> provided GUEST_TSC_FREQ MSR (C001_0134h). As paravirt clock(kvm-clock) has over-ridden
> x86_platform.calibrate_cpu() and x86_platform.calibrate_tsc() callbacks,
> SecureTSC needs to override them with its own callbacks.
Not really.
It's like you're in a contest of "how to write a commit message which is the
shortest and has as less information as possible."
Go back, read the subthread and summarize, please, what has been discussed
here and for patch 12.
I'm missing the big picture about the relationship between kvmclock and TSC
in STSC guests.
After asking so many questions, it sounds to me like this patch and patch 12
should be merged into one and there it should be explained what the strategy
is when a STSC guest loads and how kvmclock is supposed to be handled, what is
allowed, what is warned about, when the guest terminates what is tainted,
yadda yadda.
This all belongs in a single patch logically.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
