All of lore.kernel.org
 help / color / mirror / Atom feed
From: Beata Michalska <beata.michalska@arm.com>
To: Prashant Malani <pmalani@google.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Jie Zhan <zhanjie9@hisilicon.com>,
	Ionela Voinescu <ionela.voinescu@arm.com>,
	Ben Segall <bsegall@google.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Ingo Molnar <mingo@redhat.com>,
	Juri Lelli <juri.lelli@redhat.com>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:CPU FREQUENCY SCALING FRAMEWORK"
	<linux-pm@vger.kernel.org>, Mel Gorman <mgorman@suse.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Valentin Schneider <vschneid@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	z00813676 <zhenglifeng1@huawei.com>,
	sudeep.holla@arm.com
Subject: Re: [PATCH v2 2/2] cpufreq: CPPC: Dont read counters for idle CPUs
Date: Thu, 7 Aug 2025 12:24:32 +0200	[thread overview]
Message-ID: <aJR-4J-sTpLaNIJB@arm.com> (raw)
In-Reply-To: <CAFivqmLSp6RwfsPBK0d=zvRd6M_5GoeU4jHb-0OM9BpaDeSrzA@mail.gmail.com>

On Wed, Aug 06, 2025 at 05:01:48PM -0700, Prashant Malani wrote:
> Hi Beata,
> 
> On Wed, 6 Aug 2025 at 00:22, Beata Michalska <beata.michalska@arm.com> wrote:
> > Would you mind giving it a go and see whether that improves things on your end ?
> > Note that this is a quick and semi-dirty hack though.
> >
> 
> Sure.
> The provided patch doesn't appear to work as expected.
> With all cores loaded (stress_ng --cpu N), it's returning the same
> counter values
> across samples. Here are readings from multiple CPUs:
> 
> t0: del:18446603338626579088, ref:192
> t1: del:18446603338626579088, ref:192
> ref_perf:10
> delivered_perf:0
> 
> 
> t0: del:18446603338627594896, ref:192
> t1: del:18446603338627594896, ref:192
> ref_perf:10
> delivered_perf:0
> 
> t0: del:18446603338627627664, ref:192
> t1: del:18446603338627627664, ref:192
> ref_perf:10
> delivered_perf:0
> 
> I verified separately that the "burst_read" path is being used by the platform
> I am testing on.
> 
> BR,
>
> -Prashant
Right .... that's what happens when you are (I am) making last minute clean up.
That should fix it. Would you mind giving it another go ? Would appreciate it.

---
BR
Beata

diff --git a/arch/arm64/kernel/topology.c b/arch/arm64/kernel/topology.c
index 65adb78a9a87..2a51e93fcd6c 100644
--- a/arch/arm64/kernel/topology.c
+++ b/arch/arm64/kernel/topology.c
@@ -543,7 +543,7 @@ void counters_burst_read_on_cpu(void *arg)
 
 static inline bool cpc_reg_supported(struct cpc_reg *reg)
 {
-       return !((u64)reg->address != 0x0 || (u64)reg->address != 0x1);
+       return !((u64)reg->address != 0x0 && (u64)reg->address != 0x1);
 }
 
 int cpc_burst_read_ffh(int cpu, struct cpc_reg_sample *samples, size_t count)

  reply	other threads:[~2025-08-07 10:25 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  0:09 [PATCH v2 0/2] cpufreq: CPPC: idle cpu perf handling Prashant Malani
2025-06-19  0:09 ` [PATCH v2 1/2] sched: Expose idle_cpu() to modules Prashant Malani
2025-06-19  0:09 ` [PATCH v2 2/2] cpufreq: CPPC: Dont read counters for idle CPUs Prashant Malani
2025-06-20  3:53   ` Jie Zhan
2025-06-20  5:07     ` Prashant Malani
2025-06-26 18:42       ` Prashant Malani
2025-06-27  7:54       ` Jie Zhan
2025-06-27 17:07         ` Prashant Malani
2025-07-02 18:38           ` Prashant Malani
2025-07-03  9:29             ` Beata Michalska
2025-07-07  8:32             ` Beata Michalska
2025-07-09 17:25               ` Prashant Malani
2025-07-09 22:49                 ` Prashant Malani
2025-07-14  9:30                   ` Beata Michalska
2025-07-15  6:28                     ` Prashant Malani
2025-07-21 17:00                       ` Rafael J. Wysocki
2025-07-21 19:40                         ` Prashant Malani
2025-07-22  3:27                           ` Viresh Kumar
2025-07-22  6:02                             ` Prashant Malani
2025-07-30  7:31                               ` Prashant Malani
2025-07-31  8:27                                 ` Beata Michalska
2025-07-31 11:13                                   ` Viresh Kumar
2025-07-31 20:23                                     ` Beata Michalska
2025-08-01  4:43                                       ` Viresh Kumar
2025-08-07  0:19                                         ` Prashant Malani
2025-08-11  6:05                                           ` Viresh Kumar
2025-08-11 18:43                                             ` Prashant Malani
2025-08-11 19:19                                               ` Rafael J. Wysocki
2025-08-11 20:01                                                 ` Prashant Malani
2025-08-14 11:48                                                   ` Rafael J. Wysocki
2025-08-15  5:12                                                     ` Prashant Malani
2025-08-16  8:25                                                       ` Prashant Malani
2025-08-13 10:12                                               ` Beata Michalska
2025-07-31 16:51                                   ` Prashant Malani
2025-07-31 20:30                                     ` Beata Michalska
2025-08-01  9:16                                       ` Prashant Malani
2025-08-04 20:55                                         ` Prashant Malani
2025-08-06  7:21                                           ` Beata Michalska
2025-08-07  0:01                                             ` Prashant Malani
2025-08-07 10:24                                               ` Beata Michalska [this message]
2025-08-08  2:14                                                 ` Prashant Malani
2025-08-13 10:15                                                   ` Beata Michalska
2025-08-13 22:25                                                     ` Prashant Malani
2025-07-07  8:35         ` Beata Michalska

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=aJR-4J-sTpLaNIJB@arm.com \
    --to=beata.michalska@arm.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=ionela.voinescu@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=pmalani@google.com \
    --cc=rafael@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sudeep.holla@arm.com \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=zhanjie9@hisilicon.com \
    --cc=zhenglifeng1@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.