From: Ansuel Smith <ansuelsmth@gmail.com>
To: Chanwoo Choi <cwchoi00@gmail.com>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Sibi Sankar <sibis@codeaurora.org>,
Saravana Kannan <skannan@codeaurora.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/4] PM / devfreq: Fix cpufreq passive unregister erroring on PROBE_DEFER
Date: Wed, 15 Jun 2022 11:13:06 +0200 [thread overview]
Message-ID: <62a9ade8.1c69fb81.76bfd.ae0b@mx.google.com> (raw)
In-Reply-To: <17cb21c6-317a-3f70-8c4d-4d8fe20604d4@gmail.com>
On Wed, Jun 15, 2022 at 03:48:03PM +0900, Chanwoo Choi wrote:
> On 22. 6. 15. 08:09, Christian 'Ansuel' Marangi wrote:
> > With the passive governor, the cpu based scaling can PROBE_DEFER due to
> > the fact that CPU policy are not ready.
> > The cpufreq passive unregister notifier is called both from the
> > GOV_START errors and for the GOV_STOP and assume the notifier is
> > successfully registred every time. With GOV_START failing it's wrong to
> > loop over each possible CPU since the register path has failed for
> > some CPU policy not ready. Change the logic and unregister the notifer
> > based on the current allocated parent_cpu_data list to correctly handle
> > errors and the governor unregister path.
> >
> > Fixes: a03dacb0316f ("PM / devfreq: Add cpu based scaling support to passive governor")
> > Signed-off-by: Christian 'Ansuel' Marangi <ansuelsmth@gmail.com>
> > ---
> > drivers/devfreq/governor_passive.c | 39 +++++++++++++-----------------
> > 1 file changed, 17 insertions(+), 22 deletions(-)
> >
> > diff --git a/drivers/devfreq/governor_passive.c b/drivers/devfreq/governor_passive.c
> > index 72c67979ebe1..95de336f20d5 100644
> > --- a/drivers/devfreq/governor_passive.c
> > +++ b/drivers/devfreq/governor_passive.c
> > @@ -34,6 +34,20 @@ get_parent_cpu_data(struct devfreq_passive_data *p_data,
> > return NULL;
> > }
> >
> > +static void delete_parent_cpu_data(struct devfreq_passive_data *p_data)
> > +{
> > + struct devfreq_cpu_data *parent_cpu_data, *tmp;
> > +
>
> Need to add the validation checking of argument as following:
>
> if (!p_data)
> return;
>
Considering this is called only by cpufreq_passive_unregister_notifier
and cpufreq_passive_unregister_notifier is called only by devfreq_passive_event_handler
where the check is already done, isn't that redundant.
We should never reach delete_parent_cpu_data with no p_data.
(Unless you want to use that function somewhere else)
> > + list_for_each_entry_safe(parent_cpu_data, tmp, &p_data->cpu_data_list, node) {
> > + list_del(&parent_cpu_data->node);
> > +
> > + if (parent_cpu_data->opp_table)
> > + dev_pm_opp_put_opp_table(parent_cpu_data->opp_table);
> > +
> > + kfree(parent_cpu_data);
> > + }
> > +}
> > +
> > static unsigned long get_target_freq_by_required_opp(struct device *p_dev,
> > struct opp_table *p_opp_table,
> > struct opp_table *opp_table,
> > @@ -222,8 +236,7 @@ static int cpufreq_passive_unregister_notifier(struct devfreq *devfreq)
> > {
> > struct devfreq_passive_data *p_data
> > = (struct devfreq_passive_data *)devfreq->data;
> > - struct devfreq_cpu_data *parent_cpu_data;
> > - int cpu, ret = 0;
> > + int ret;
> >
> > if (p_data->nb.notifier_call) {
> > ret = cpufreq_unregister_notifier(&p_data->nb,
> > @@ -232,27 +245,9 @@ static int cpufreq_passive_unregister_notifier(struct devfreq *devfreq)
> > return ret;
> > }
> >
> > - for_each_possible_cpu(cpu) {
> > - struct cpufreq_policy *policy = cpufreq_cpu_get(cpu);
> > - if (!policy) {
> > - ret = -EINVAL;
> > - continue;
> > - }
> > -
> > - parent_cpu_data = get_parent_cpu_data(p_data, policy);
> > - if (!parent_cpu_data) {
> > - cpufreq_cpu_put(policy);
> > - continue;
> > - }
> > -
> > - list_del(&parent_cpu_data->node);
> > - if (parent_cpu_data->opp_table)
> > - dev_pm_opp_put_opp_table(parent_cpu_data->opp_table);
> > - kfree(parent_cpu_data);
> > - cpufreq_cpu_put(policy);
> > - }
> > + delete_parent_cpu_data(p_data);
> >
> > - return ret;
> > + return 0;
> > }
> >
> > static int cpufreq_passive_register_notifier(struct devfreq *devfreq)
>
>
> --
> Best Regards,
> Samsung Electronics
> Chanwoo Choi
--
Ansuel
next prev parent reply other threads:[~2022-06-15 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 23:09 [PATCH v4 0/4] PM / devfreq: Various Fixes to cpufreq based passive governor Christian 'Ansuel' Marangi
2022-06-14 23:09 ` [PATCH v4 1/4] PM / devfreq: Fix cpufreq passive unregister erroring on PROBE_DEFER Christian 'Ansuel' Marangi
2022-06-15 6:48 ` Chanwoo Choi
2022-06-15 9:13 ` Ansuel Smith [this message]
2022-06-17 18:35 ` Chanwoo Choi
2022-06-14 23:09 ` [PATCH v4 2/4] PM / devfreq: Fix kernel warning with cpufreq passive register fail Christian 'Ansuel' Marangi
2022-06-15 7:11 ` Chanwoo Choi
2022-06-15 9:20 ` Ansuel Smith
2022-06-17 19:08 ` Chanwoo Choi
2022-06-19 22:19 ` Christian Marangi
2022-06-14 23:09 ` [PATCH v4 3/4] PM / devfreq: Rework freq_table to be local to devfreq struct Christian 'Ansuel' Marangi
2022-06-17 19:33 ` Chanwoo Choi
2022-06-17 19:38 ` Christian Marangi
2022-06-18 13:57 ` Chanwoo Choi
2022-06-14 23:09 ` [PATCH v4 4/4] PM / devfreq: Mute warning on governor PROBE_DEFER Christian 'Ansuel' Marangi
2022-06-15 6:56 ` Chanwoo Choi
2022-06-15 9:22 ` Ansuel Smith
2022-06-17 18:09 ` Chanwoo Choi
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=62a9ade8.1c69fb81.76bfd.ae0b@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=cwchoi00@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=sibis@codeaurora.org \
--cc=skannan@codeaurora.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