summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/flamegraph.py
diff options
context:
space:
mode:
authorLuka Absandze <absandze@amazon.de>2026-09-20 15:54:53 +0000
committerSean Christopherson <seanjc@google.com>2026-09-28 16:41:44 -0700
commit1c24893fdb4df1e8713d921a849ef14626e50954 (patch)
tree4daf780df6b1dd1f92e72df77249c725d6d3b51f /tools/perf/scripts/python/flamegraph.py
parent0d7fbc059f33527caadf1f0387d3eea61962c402 (diff)
KVM: x86/pmu: Don't retry a counter whose config was rejected
kvm_pmu_handle_event() re-arms the reprogram bit for every failed reprogram, on the assumption that the failure is transient and a later refresh will succeed. That is true for contention, e.g. the -EBUSY from x86_reserve_hardware(), but not for a configuration the host PMU driver rejects outright. A rejected config can never succeed on retry, so the counter is reprogrammed on every PMU refresh for as long as the guest leaves it enabled, and every attempt fails the same way. Re-arm only for the errnos that indicate a transient condition, i.e. -EBUSY and -ENOMEM. Suggested-by: Sean Christopherson <seanjc@google.com> Link: https://lore.kernel.org/all/20260916123315.89042-1-absandze@amazon.de/ Signed-off-by: Luka Absandze <absandze@amazon.de> Reviewed-by: Sandipan Das <sandipan.das@amd.com> Link: https://patch.msgid.link/20260920155453.10836-1-absandze@amazon.de Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions