Thread (42 messages) 42 messages, 5 authors, 2025-02-12

Re: [PATCH 16/16] x86/kvmclock: Use TSC for sched_clock if it's constant and non-stop

From: Sean Christopherson <seanjc@google.com>
Date: 2025-02-12 22:55:42
Also in: kvm, linux-coco, lkml, virtualization, xen-devel

On Wed, Feb 12, 2025, Michael Kelley wrote:
From: Sean Christopherson <seanjc@google.com> Sent: Monday, February 10, 2025 8:22 AM
quoted
On Sat, Feb 08, 2025, Michael Kelley wrote:
quoted
But I would be good with some restructuring so that setting the sched clock
save/restore hooks is more closely tied to the sched clock choice,
Yeah, this is the intent of my ranting.  After the dust settles, the code can
look like this.
I'm good with what you are proposing. And if you want, there's no real need
for hv_ref_counter_at_suspend and hv_save/restore_sched_clock_state()
to be in the #ifdef sequence since the code has no architecture dependencies.
Right, but because they will be local/static and there are no users outside of
x86, the compiler will complain about unused variables/functions on other
architectures.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help