summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/intel-pt-events.py
diff options
context:
space:
mode:
authorAkihiko Odaki <akihiko.odaki@daynix.com>2025-03-15 12:12:13 +0300
committerOliver Upton <oliver.upton@linux.dev>2025-03-17 20:45:25 +0300
commit1db4aaa05589454c674b1c117263997dcac515f3 (patch)
tree0be9715492061bbb3605bbfb528dac4182834340 /tools/perf/scripts/python/intel-pt-events.py
parent64074ca8ca92b8e6b6f76f5ea6982cd55bbc27bf (diff)
downloadlinux-1db4aaa05589454c674b1c117263997dcac515f3.tar.xz
KVM: arm64: PMU: Reload when user modifies registers
Commit d0c94c49792c ("KVM: arm64: Restore PMU configuration on first run") added the code to reload the PMU configuration on first run. It is also important to keep the correct state even if system registers are modified after first run, specifically when debugging Windows on QEMU with GDB; QEMU tries to write back all visible registers when resuming the VM execution with GDB, corrupting the PMU state. Windows always uses the PMU so this can cause adverse effects on that particular OS. The usual register writes and reset are already handled independently, but register writes from userspace are not covered. Trigger the code to reload the PMU configuration for them instead so that PMU configuration changes made by users will be applied also after the first run. Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com> Reviewed-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/r/20250315-pmc-v5-4-ecee87dab216@daynix.com Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
Diffstat (limited to 'tools/perf/scripts/python/intel-pt-events.py')
0 files changed, 0 insertions, 0 deletions