From: Gautam Menghani <gautam@linux.ibm.com>
To: maddy@linux.ibm.com, npiggin@gmail.com, mpe@ellerman.id.au,
chleroy@kernel.org, ritesh.list@gmail.com, sshegde@linux.ibm.com,
atrajeev@linux.ibm.com, tshah@linux.ibm.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: [PATCH v3 1/3] Revert "powerpc/perf: Add per-task/process monitoring to vpa_pmu driver"
Date: Fri, 6 Nov 2026 21:01:32 +0530 [thread overview]
Message-ID: <20261106153136.330165-2-gautam@linux.ibm.com> (raw)
In-Reply-To: <20261106153136.330165-1-gautam@linux.ibm.com>
This reverts commit f26f9933e3e31b2117b804b6b8932388db88a131.
The local_paca holds a pointer to the vCPU currently running on the given
host CPU. When the vpa-pmu driver tries to get the vCPU pointer from
local_paca, it either receives NULL or the pointer to the vCPU which was
running on that host CPU previously. This is because the vCPU pointer in
PACA is updated by kvmhv_run_single_vcpu(), which runs after
vpa_pmu_add(). Also, on vCPU exit, the vCPU pointer in PACA is never
cleared. This results in incorrect numbers being reported by the vpa-pmu
driver.
Fix the problem by avoiding the use of vCPU pointer in PACA altogether.
When a vCPU is scheduled in and out on a host vCPU, vpa_pmu_add() and
vpa_pmu_del() can already calculate the correct latency values in
event->count. Drop the usage of the vCPU pointer in PACA and just rely
on the VPA counter values.
Fixes: f26f9933e3e3 ("powerpc/perf: Add per-task/process monitoring to vpa_pmu driver")
Cc: <stable@vger.kernel.org>
Signed-off-by: Gautam Menghani <gautam@linux.ibm.com>
---
arch/powerpc/include/asm/kvm_book3s_64.h | 3 --
arch/powerpc/kvm/book3s_hv.c | 45 ------------------------
arch/powerpc/perf/vpa-pmu.c | 15 ++------
3 files changed, 3 insertions(+), 60 deletions(-)
diff --git a/arch/powerpc/include/asm/kvm_book3s_64.h b/arch/powerpc/include/asm/kvm_book3s_64.h
index b936e174eefd..f620e3126d68 100644
--- a/arch/powerpc/include/asm/kvm_book3s_64.h
+++ b/arch/powerpc/include/asm/kvm_book3s_64.h
@@ -691,9 +691,6 @@ void kvmhv_set_l2_counters_status(int cpu, bool status);
u64 kvmhv_get_l1_to_l2_cs_time(void);
u64 kvmhv_get_l2_to_l1_cs_time(void);
u64 kvmhv_get_l2_runtime_agg(void);
-u64 kvmhv_get_l1_to_l2_cs_time_vcpu(void);
-u64 kvmhv_get_l2_to_l1_cs_time_vcpu(void);
-u64 kvmhv_get_l2_runtime_agg_vcpu(void);
#endif /* CONFIG_KVM_BOOK3S_HV_POSSIBLE */
diff --git a/arch/powerpc/kvm/book3s_hv.c b/arch/powerpc/kvm/book3s_hv.c
index 22283d46e8fe..5fa6f93548ad 100644
--- a/arch/powerpc/kvm/book3s_hv.c
+++ b/arch/powerpc/kvm/book3s_hv.c
@@ -4212,51 +4212,6 @@ u64 kvmhv_get_l2_runtime_agg(void)
}
EXPORT_SYMBOL(kvmhv_get_l2_runtime_agg);
-u64 kvmhv_get_l1_to_l2_cs_time_vcpu(void)
-{
- struct kvm_vcpu *vcpu;
- struct kvm_vcpu_arch *arch;
-
- vcpu = local_paca->kvm_hstate.kvm_vcpu;
- if (vcpu) {
- arch = &vcpu->arch;
- return arch->l1_to_l2_cs;
- } else {
- return 0;
- }
-}
-EXPORT_SYMBOL(kvmhv_get_l1_to_l2_cs_time_vcpu);
-
-u64 kvmhv_get_l2_to_l1_cs_time_vcpu(void)
-{
- struct kvm_vcpu *vcpu;
- struct kvm_vcpu_arch *arch;
-
- vcpu = local_paca->kvm_hstate.kvm_vcpu;
- if (vcpu) {
- arch = &vcpu->arch;
- return arch->l2_to_l1_cs;
- } else {
- return 0;
- }
-}
-EXPORT_SYMBOL(kvmhv_get_l2_to_l1_cs_time_vcpu);
-
-u64 kvmhv_get_l2_runtime_agg_vcpu(void)
-{
- struct kvm_vcpu *vcpu;
- struct kvm_vcpu_arch *arch;
-
- vcpu = local_paca->kvm_hstate.kvm_vcpu;
- if (vcpu) {
- arch = &vcpu->arch;
- return arch->l2_runtime_agg;
- } else {
- return 0;
- }
-}
-EXPORT_SYMBOL(kvmhv_get_l2_runtime_agg_vcpu);
-
#else
int kvmhv_get_l2_counters_status(void)
{
diff --git a/arch/powerpc/perf/vpa-pmu.c b/arch/powerpc/perf/vpa-pmu.c
index bff4cfab7b94..01d9196fcb0f 100644
--- a/arch/powerpc/perf/vpa-pmu.c
+++ b/arch/powerpc/perf/vpa-pmu.c
@@ -98,22 +98,13 @@ static unsigned long get_counter_data(struct perf_event *event)
switch (config) {
case L1_TO_L2_CS_LAT:
- if (event->attach_state & PERF_ATTACH_TASK)
- data = kvmhv_get_l1_to_l2_cs_time_vcpu();
- else
- data = kvmhv_get_l1_to_l2_cs_time();
+ data = kvmhv_get_l1_to_l2_cs_time();
break;
case L2_TO_L1_CS_LAT:
- if (event->attach_state & PERF_ATTACH_TASK)
- data = kvmhv_get_l2_to_l1_cs_time_vcpu();
- else
- data = kvmhv_get_l2_to_l1_cs_time();
+ data = kvmhv_get_l2_to_l1_cs_time();
break;
case L2_RUNTIME_AGG:
- if (event->attach_state & PERF_ATTACH_TASK)
- data = kvmhv_get_l2_runtime_agg_vcpu();
- else
- data = kvmhv_get_l2_runtime_agg();
+ data = kvmhv_get_l2_runtime_agg();
break;
default:
data = 0;
--
2.56.0
next prev parent reply other threads:[~2026-11-06 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 15:31 [PATCH v3 0/3] powerpc/perf: Fix vpa-pmu driver to report correct numbers Gautam Menghani
2026-11-06 15:31 ` Gautam Menghani [this message]
2026-11-06 15:31 ` [PATCH v3 2/3] powerpc/perf: Update prev_count of event to get accurate values Gautam Menghani
2026-11-06 15:31 ` [PATCH v3 3/3] KVM: PPC: Book3s HV: Ensure reliable usage of latency counters Gautam Menghani
2026-11-06 16:02 ` [PATCH v3 0/3] powerpc/perf: Fix vpa-pmu driver to report correct numbers Gautam Menghani
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=20261106153136.330165-2-gautam@linux.ibm.com \
--to=gautam@linux.ibm.com \
--cc=atrajeev@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=ritesh.list@gmail.com \
--cc=sshegde@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=tshah@linux.ibm.com \
/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®