From: Luka Absandze <absandze@amazon.de>
To: <seanjc@google.com>, <pbonzini@redhat.com>
Cc: <sandipan.das@amd.com>, <tglx@kernel.org>, <mingo@redhat.com>,
<bp@alien8.de>, <dave.hansen@linux.intel.com>, <x86@kernel.org>,
<hpa@zytor.com>, <dwmw2@infradead.org>, <kvm@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
"Luka Absandze" <absandze@amazon.de>
Subject: [PATCH v2] KVM: x86/pmu: Don't retry a counter whose config was rejected
Date: Sun, 20 Sep 2026 15:54:53 +0000 [thread overview]
Message-ID: <20260920155453.10836-1-absandze@amazon.de> (raw)
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>
---
v2:
- Use an allow-list of transient errnos (-EBUSY, -ENOMEM) rather than
excluding -EINVAL, and hoist 'r' out of the loop. Diff taken from
Sean's suggestion verbatim. [Sean]
- Reword the comment to say "fails on a transient condition". [Sean]
- v1: https://lore.kernel.org/all/20260918160006.61816-1-absandze@amazon.de/
diff --git a/arch/x86/kvm/pmu.c b/arch/x86/kvm/pmu.c
index a7d60c8785cd..03a470c49a74 100644
--- a/arch/x86/kvm/pmu.c
+++ b/arch/x86/kvm/pmu.c
@@ -662,7 +662,7 @@ void kvm_pmu_handle_event(struct kvm_vcpu *vcpu)
DECLARE_BITMAP(bitmap, X86_PMC_IDX_MAX);
struct kvm_pmu *pmu = vcpu_to_pmu(vcpu);
struct kvm_pmc *pmc;
- int bit;
+ int bit, r;
bitmap_copy(bitmap, pmu->reprogram_pmi, X86_PMC_IDX_MAX);
@@ -676,12 +676,14 @@ void kvm_pmu_handle_event(struct kvm_vcpu *vcpu)
kvm_for_each_pmc(pmu, pmc, bit, bitmap) {
/*
- * If reprogramming fails, e.g. due to contention, re-set the
- * reprogram bit, i.e. opportunistically try again on the next
- * PMU refresh. Don't make a new request as doing so can stall
- * the guest if reprogramming repeatedly fails.
+ * If reprogramming fails on a transient condition, e.g. due to
+ * contention, re-set the reprogram bit, i.e. opportunistically
+ * try again on the next PMU refresh. Don't make a new request
+ * as doing so can stall the guest if reprogramming repeatedly
+ * fails.
*/
- if (reprogram_counter(pmc))
+ r = reprogram_counter(pmc);
+ if (r == -EBUSY || r == -ENOMEM)
set_bit(pmc->idx, pmu->reprogram_pmi);
}
--
2.47.3
next reply other threads:[~2026-09-20 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 15:54 Luka Absandze [this message]
2026-09-21 5:10 ` Sandipan Das
2026-09-21 5:11 ` Sandipan Das
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260920155453.10836-1-absandze@amazon.de \
--to=absandze@amazon.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sandipan.das@amd.com \
--cc=seanjc@google.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®