summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/gecko.py
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2025-03-19 16:11:59 +0300
committerPaolo Bonzini <pbonzini@redhat.com>2025-03-19 16:11:59 +0300
commitfcce7c1e7d39bc35651ad0fbdeaa15276ea7fb15 (patch)
treec373fe8fdcf2fae6ed35f1f523f455f48095e05b /tools/perf/scripts/python/gecko.py
parent9b093f5b86fb0bfd4d819dd2741893de69f111d9 (diff)
parent1b3c38050b5cc07f6873f244f845fb6c8549ce85 (diff)
downloadlinux-fcce7c1e7d39bc35651ad0fbdeaa15276ea7fb15.tar.xz
Merge tag 'kvm-x86-pvclock-6.15' of https://github.com/kvm-x86/linux into HEAD
KVM PV clock changes for 6.15: - Don't take kvm->lock when iterating over vCPUs in the suspend notifier to fix a largely theoretical deadlock. - Use the vCPU's actual Xen PV clock information when starting the Xen timer, as the cached state in arch.hv_clock can be stale/bogus. - Fix a bug where KVM could bleed PVCLOCK_GUEST_STOPPED across different PV clocks. - Restrict PVCLOCK_GUEST_STOPPED to kvmclock, as KVM's suspend notifier only accounts for kvmclock, and there's no evidence that the flag is actually supported by Xen guests. - Clean up the per-vCPU "cache" of its reference pvclock, and instead only track the vCPU's TSC scaling (multipler+shift) metadata (which is moderately expensive to compute, and rarely changes for modern setups).
Diffstat (limited to 'tools/perf/scripts/python/gecko.py')
0 files changed, 0 insertions, 0 deletions