From: Pierre Gondois <pierre.gondois@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
vschneid@redhat.com, sudeep.holla@arm.com,
gregkh@linuxfoundation.org, rafael@kernel.org,
linux-kernel@vger.kernel.org
Cc: lukasz.luba@arm.com, ionela.voinescu@arm.com
Subject: Re: [Resend PATCH] topology: Set capacity_freq_ref in all cases
Date: Thu, 18 Jan 2024 18:36:14 +0100 [thread overview]
Message-ID: <82d272fb-ffc3-4d55-b92a-497cbc13fc03@arm.com> (raw)
In-Reply-To: <20240117190545.596057-1-vincent.guittot@linaro.org>
Tested-by: Pierre Gondois <pierre.gondois@arm.com>
On 1/17/24 20:05, Vincent Guittot wrote:
> If "capacity-dmips-mhz" is not set, raw_capacity is null and we skip the
> normalization step which includes setting per_cpu capacity_freq_ref.
> Always register the notifier but skip the capacity normalization if
> raw_capacity is null.
>
> Fixes: 9942cb22ea45 ("sched/topology: Add a new arch_scale_freq_ref() method")
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
> ---
>
> Resend with correct email address for Sudeep
>
> drivers/base/arch_topology.c | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
> index 5aaa0865625d..2aa0c6425290 100644
> --- a/drivers/base/arch_topology.c
> +++ b/drivers/base/arch_topology.c
> @@ -417,9 +417,6 @@ init_cpu_capacity_callback(struct notifier_block *nb,
> struct cpufreq_policy *policy = data;
> int cpu;
>
> - if (!raw_capacity)
> - return 0;
> -
> if (val != CPUFREQ_CREATE_POLICY)
> return 0;
>
> @@ -436,9 +433,11 @@ init_cpu_capacity_callback(struct notifier_block *nb,
> }
>
> if (cpumask_empty(cpus_to_visit)) {
> - topology_normalize_cpu_scale();
> - schedule_work(&update_topology_flags_work);
> - free_raw_capacity();
> + if (raw_capacity) {
> + topology_normalize_cpu_scale();
> + schedule_work(&update_topology_flags_work);
> + free_raw_capacity();
> + }
> pr_debug("cpu_capacity: parsing done\n");
> schedule_work(&parsing_done_work);
> }
> @@ -458,7 +457,7 @@ static int __init register_cpufreq_notifier(void)
> * On ACPI-based systems skip registering cpufreq notifier as cpufreq
> * information is not needed for cpu capacity initialization.
> */
> - if (!acpi_disabled || !raw_capacity)
> + if (!acpi_disabled)
> return -EINVAL;
>
> if (!alloc_cpumask_var(&cpus_to_visit, GFP_KERNEL))
next prev parent reply other threads:[~2024-01-18 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 19:05 [Resend PATCH] topology: Set capacity_freq_ref in all cases Vincent Guittot
2024-01-18 9:42 ` Sudeep Holla
2024-01-18 12:10 ` Dietmar Eggemann
2024-01-18 17:36 ` Pierre Gondois [this message]
2024-01-23 15:14 ` Mark Brown
2024-01-23 16:23 ` Paul Barker
2024-02-13 11:06 ` Paul Barker
2024-02-13 11:45 ` Greg KH
2024-01-31 13:56 ` Erico Nunes
2024-01-31 14:55 ` Vincent Guittot
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=82d272fb-ffc3-4d55-b92a-497cbc13fc03@arm.com \
--to=pierre.gondois@arm.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=ionela.voinescu@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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