From: Beata Michalska <beata.michalska@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
ionela.voinescu@arm.com, sudeep.holla@arm.com, will@kernel.org,
catalin.marinas@arm.com, rafael@kernel.org, sumitg@nvidia.com,
yang@os.amperecomputing.com, vanshikonda@os.amperecomputing.com,
lihuisong@huawei.com, zhanjie9@hisilicon.com
Subject: Re: [PATCH v9 1/5] cpufreq: Allow arch_freq_get_on_cpu to return an error
Date: Thu, 23 Jan 2025 22:45:12 +0100 [thread overview]
Message-ID: <Z5K4aDaZIbhRCbOP@arm.com> (raw)
In-Reply-To: <20250122061250.kxdpkkvce4g5nar2@vireshk-i7>
On Wed, Jan 22, 2025 at 11:42:50AM +0530, Viresh Kumar wrote:
> On 21-01-25, 16:14, Beata Michalska wrote:
> > Theoretically speaking - it should, though what would 0 actually
> > represent then ?
>
> 0 won't be a failure, that's clear, since errors are represented
> differently now. I am not sure what 0 frequency would mean and it can
> be left as an architecture specific value, which is a corner case I am
> not sure will ever occur.
That would mean we are opting for presenting '0' value (whatever that means)
instead of trying alternative ways of getting 'current' frequency ?
This is still the scaling_cur_freq.
---
BR
Beata
>
> --
> viresh
next prev parent reply other threads:[~2025-01-23 21:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 8:44 [PATCH v9 0/5] Add support for AArch64 AMUv1-based average freq Beata Michalska
2025-01-21 8:44 ` [PATCH v9 1/5] cpufreq: Allow arch_freq_get_on_cpu to return an error Beata Michalska
2025-01-21 10:47 ` Viresh Kumar
2025-01-21 15:14 ` Beata Michalska
2025-01-21 18:40 ` Vanshidhar Konda
2025-01-23 21:37 ` Beata Michalska
2025-01-22 6:12 ` Viresh Kumar
2025-01-23 21:45 ` Beata Michalska [this message]
2025-01-24 3:33 ` Viresh Kumar
2025-01-28 8:09 ` Beata Michalska
2025-01-28 8:18 ` Viresh Kumar
2025-01-21 10:47 ` Prasanna Kumar T S M
2025-01-24 4:15 ` Prasanna Kumar T S M
2025-01-21 8:44 ` [PATCH v9 2/5] cpufreq: Introduce an optional cpuinfo_avg_freq sysfs entry Beata Michalska
2025-01-21 10:53 ` Viresh Kumar
2025-01-21 15:17 ` Beata Michalska
2025-01-22 6:09 ` Viresh Kumar
2025-01-23 21:47 ` Beata Michalska
2025-01-24 3:27 ` Viresh Kumar
2025-01-28 8:43 ` Prasanna Kumar T S M
2025-01-29 11:29 ` Sumit Gupta
2025-01-21 8:44 ` [PATCH v9 3/5] arm64: amu: Delay allocating cpumask for AMU FIE support Beata Michalska
2025-01-24 4:48 ` Prasanna Kumar T S M
2025-01-29 11:17 ` Sumit Gupta
2025-01-21 8:44 ` [PATCH v9 4/5] arm64: Provide an AMU-based version of arch_freq_get_on_cpu Beata Michalska
2025-01-24 4:43 ` Prasanna Kumar T S M
2025-01-28 8:16 ` Beata Michalska
2025-01-28 8:52 ` Prasanna Kumar T S M
2025-01-29 11:15 ` Sumit Gupta
2025-01-21 8:44 ` [PATCH v9 5/5] arm64: Update AMU-based freq scale factor on entering idle Beata Michalska
2025-01-24 4:45 ` Prasanna Kumar T S M
2025-01-29 11:13 ` Sumit Gupta
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=Z5K4aDaZIbhRCbOP@arm.com \
--to=beata.michalska@arm.com \
--cc=catalin.marinas@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=lihuisong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=sumitg@nvidia.com \
--cc=vanshikonda@os.amperecomputing.com \
--cc=viresh.kumar@linaro.org \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.com \
--cc=zhanjie9@hisilicon.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;
as well as URLs for NNTP newsgroup(s).