summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/check-perf-trace.py
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2025-03-19 16:14:59 +0300
committerPaolo Bonzini <pbonzini@redhat.com>2025-03-19 16:14:59 +0300
commit3ecf162a3162d9ec8ec6ef6e12a722e6255940d5 (patch)
treef89b6851c631b4818ef4a9c4995002355a16df80 /tools/perf/scripts/python/check-perf-trace.py
parentfcce7c1e7d39bc35651ad0fbdeaa15276ea7fb15 (diff)
parenta2b00f85d7839d74a2f6fcbf547d4bf2e82c34e5 (diff)
downloadlinux-3ecf162a3162d9ec8ec6ef6e12a722e6255940d5.tar.xz
Merge tag 'kvm-x86-xen-6.15' of https://github.com/kvm-x86/linux into HEAD
KVM Xen changes for 6.15 - Don't write to the Xen hypercall page on MSR writes that are initiated by the host (userspace or KVM) to fix a class of bugs where KVM can write to guest memory at unexpected times, e.g. during vCPU creation if userspace has set the Xen hypercall MSR index to collide with an MSR that KVM emulates. - Restrict the Xen hypercall MSR indx to the unofficial synthetic range to reduce the set of possible collisions with MSRs that are emulated by KVM (collisions can still happen as KVM emulates Hyper-V MSRs, which also reside in the synthetic range). - Clean up and optimize KVM's handling of Xen MSR writes and xen_hvm_config. - Update Xen TSC leaves during CPUID emulation instead of modifying the CPUID entries when updating PV clocks, as there is no guarantee PV clocks will be updated between TSC frequency changes and CPUID emulation, and guest reads of Xen TSC should be rare, i.e. are not a hot path.
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions