From: Viresh Kumar <viresh.kumar@linaro.org>
To: Ionela Voinescu <ionela.voinescu@arm.com>
Cc: rjw@rjwysocki.net, dietmar.eggemann@arm.com,
catalin.marinas@arm.com, sudeep.holla@arm.com, will@kernel.org,
valentin.schneider@arm.com, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] arch_topology: validate input frequencies to arch_set_freq_scale()
Date: Tue, 25 Aug 2020 11:26:18 +0530 [thread overview]
Message-ID: <20200825055618.ybght3enlpuwo3va@vireshk-i7> (raw)
In-Reply-To: <20200824210252.27486-2-ionela.voinescu@arm.com>
On 24-08-20, 22:02, Ionela Voinescu wrote:
> The current frequency passed to arch_set_freq_scale() could end up
> being 0, signaling an error in setting a new frequency. Also, if the
> maximum frequency in 0, this will result in a division by 0 error.
>
> Therefore, validate these input values before using them for the
> setting of the frequency scale factor.
>
> Signed-off-by: Ionela Voinescu <ionela.voinescu@arm.com>
> Cc: Sudeep Holla <sudeep.holla@arm.com>
> Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
> ---
> drivers/base/arch_topology.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
> index 75f72d684294..1aca82fcceb8 100644
> --- a/drivers/base/arch_topology.c
> +++ b/drivers/base/arch_topology.c
> @@ -33,6 +33,9 @@ void arch_set_freq_scale(struct cpumask *cpus, unsigned long cur_freq,
> unsigned long scale;
> int i;
>
> + if (!cur_freq || !max_freq)
We should probably use unlikely() here.
Rafael: Shouldn't this have a WARN_ON_ONCE() as well ?
> + return;
> +
> /*
> * If the use of counters for FIE is enabled, just return as we don't
> * want to update the scale factor with information from CPUFREQ.
> --
> 2.17.1
--
viresh
next prev parent reply other threads:[~2020-08-25 5:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 21:02 [PATCH v3 0/5] cpufreq: improve frequency invariance support Ionela Voinescu
2020-08-24 21:02 ` [PATCH v3 1/5] arch_topology: validate input frequencies to arch_set_freq_scale() Ionela Voinescu
2020-08-25 5:56 ` Viresh Kumar [this message]
2020-08-25 11:31 ` Ionela Voinescu
2020-08-27 6:10 ` Viresh Kumar
2020-08-24 21:02 ` [PATCH v3 2/5] cpufreq: move invariance setter calls in cpufreq core Ionela Voinescu
2020-08-25 6:03 ` Viresh Kumar
2020-08-24 21:02 ` [PATCH v3 3/5] cpufreq: report whether cpufreq supports Frequency Invariance (FI) Ionela Voinescu
2020-08-25 6:27 ` Viresh Kumar
2020-08-25 11:07 ` Ionela Voinescu
2020-08-24 21:02 ` [PATCH v3 4/5] arch_topology, cpufreq: constify arch_* cpumasks Ionela Voinescu
2020-08-25 6:27 ` Viresh Kumar
2020-08-24 21:02 ` [PATCH v3 5/5] arch_topology, arm, arm64: define arch_scale_freq_invariant() Ionela Voinescu
2020-08-25 7:50 ` Viresh Kumar
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=20200825055618.ybght3enlpuwo3va@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=valentin.schneider@arm.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).