From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: sboyd@codeaurora.org, linaro-kernel@lists.linaro.org,
patches@linaro.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] cpufreq: serialize calls to __cpufreq_governor()
Date: Tue, 03 Sep 2013 21:40:14 +0200 [thread overview]
Message-ID: <5197493.kSPF7VUWqc@vostro.rjw.lan> (raw)
In-Reply-To: <5225E205.7080008@linux.vnet.ibm.com>
On Tuesday, September 03, 2013 06:50:05 PM Srivatsa S. Bhat wrote:
> On 09/01/2013 10:56 AM, Viresh Kumar wrote:
> > We can't take a big lock around __cpufreq_governor() as this causes recursive
> > locking for some cases. But calls to this routine must be serialized for every
> > policy.
> >
> > Lets introduce another variable which would guarantee serialization here.
> >
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> > drivers/cpufreq/cpufreq.c | 7 ++++++-
> > include/linux/cpufreq.h | 1 +
> > 2 files changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> > index f320a20..4d5723db 100644
> > --- a/drivers/cpufreq/cpufreq.c
> > +++ b/drivers/cpufreq/cpufreq.c
> > @@ -1692,13 +1692,15 @@ static int __cpufreq_governor(struct cpufreq_policy *policy,
> > policy->cpu, event);
> >
> > mutex_lock(&cpufreq_governor_lock);
> > - if ((policy->governor_enabled && (event == CPUFREQ_GOV_START)) ||
> > + if (policy->governor_busy ||
> > + (policy->governor_enabled && (event == CPUFREQ_GOV_START)) ||
> > (!policy->governor_enabled && ((event == CPUFREQ_GOV_LIMITS) ||
> > (event == CPUFREQ_GOV_STOP)))) {
> > mutex_unlock(&cpufreq_governor_lock);
> > return -EBUSY;
> > }
> >
> > + policy->governor_busy = true;
> > if (event == CPUFREQ_GOV_STOP)
> > policy->governor_enabled = false;
> > else if (event == CPUFREQ_GOV_START)
> > @@ -1727,6 +1729,9 @@ static int __cpufreq_governor(struct cpufreq_policy *policy,
> > ((event == CPUFREQ_GOV_POLICY_EXIT) && !ret))
> > module_put(policy->governor->owner);
> >
> > + mutex_lock(&cpufreq_governor_lock);
> > + policy->governor_busy = false;
> > + mutex_unlock(&cpufreq_governor_lock);
> > return ret;
> > }
> >
>
> This doesn't solve the problem completely: it prevents the store_*() task
> from continuing *only* when it concurrently executes the __cpufreq_governor()
> function along with the CPU offline task. But if the two calls don't overlap,
> we will still have the possibility where the store_*() task tries to acquire
> the timer mutex after the CPU offline task has just finished destroying it.
Yeah, I overlooked that.
> So, IMHO, the right fix is to synchronize with CPU hotplug. That way, the
> store_*() thread will wait until the entire CPU offline operation is completed.
> After that, if it continues, it will get -EBUSY, due to patch [1], since
> policy->governor_enabled will be set to false.
>
> [1]. https://patchwork.kernel.org/patch/2852463/
>
> So here is the (completely untested) fix that I propose, as a replacement to
> this patch [2/2]:
That looks reasonable to me.
Viresh?
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index 5c75e31..71c4fb2 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -440,17 +440,24 @@ static ssize_t store_##file_name \
> unsigned int ret; \
> struct cpufreq_policy new_policy; \
> \
> + get_online_cpus(); \
> ret = cpufreq_get_policy(&new_policy, policy->cpu); \
> - if (ret) \
> - return -EINVAL; \
> + if (ret) { \
> + ret = -EINVAL; \
> + goto out; \
> + } \
> \
> ret = sscanf(buf, "%u", &new_policy.object); \
> - if (ret != 1) \
> - return -EINVAL; \
> + if (ret != 1) { \
> + ret = -EINVAL; \
> + goto out; \
> + } \
> \
> ret = __cpufreq_set_policy(policy, &new_policy); \
> policy->user_policy.object = policy->object; \
> \
> +out: \
> + put_online_cpus(); \
> return ret ? ret : count; \
> }
>
> @@ -494,17 +501,22 @@ static ssize_t store_scaling_governor(struct cpufreq_policy *policy,
> char str_governor[16];
> struct cpufreq_policy new_policy;
>
> + get_online_cpus();
> ret = cpufreq_get_policy(&new_policy, policy->cpu);
> if (ret)
> - return ret;
> + goto out;
>
> ret = sscanf(buf, "%15s", str_governor);
> - if (ret != 1)
> - return -EINVAL;
> + if (ret != 1) {
> + ret = -EINVAL;
> + goto out;
> + }
>
> if (cpufreq_parse_governor(str_governor, &new_policy.policy,
> - &new_policy.governor))
> - return -EINVAL;
> + &new_policy.governor)) {
> + ret = -EINVAL;
> + goto out;
> + }
>
> /*
> * Do not use cpufreq_set_policy here or the user_policy.max
> @@ -515,6 +527,9 @@ static ssize_t store_scaling_governor(struct cpufreq_policy *policy,
> policy->user_policy.policy = policy->policy;
> policy->user_policy.governor = policy->governor;
>
> +out:
> + put_online_cpus();
> +
> if (ret)
> return ret;
> else
>
>
> Regards,
> Srivatsa S. Bhat
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-09-03 19:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 5:26 [PATCH 1/2] cpufreq: don't allow governor limits to be changed when it is disabled Viresh Kumar
2013-09-01 5:26 ` [PATCH 2/2] cpufreq: serialize calls to __cpufreq_governor() Viresh Kumar
2013-09-01 13:28 ` Rafael J. Wysocki
2013-09-01 16:00 ` Viresh Kumar
2013-09-01 20:27 ` Rafael J. Wysocki
2013-09-02 1:00 ` Viresh Kumar
2013-09-02 12:44 ` Rafael J. Wysocki
2013-09-03 13:20 ` Srivatsa S. Bhat
2013-09-03 19:40 ` Rafael J. Wysocki [this message]
2013-09-13 11:44 ` Viresh Kumar
2013-09-13 23:48 ` Rafael J. Wysocki
2013-09-14 4:29 ` Viresh Kumar
2013-09-17 11:49 ` Srivatsa S. Bhat
2013-09-04 23:55 ` Rafael J. Wysocki
2013-09-04 23:50 ` Stephen Boyd
2013-09-05 0:26 ` Rafael J. Wysocki
2013-09-05 0:54 ` Stephen Boyd
2013-09-06 6:03 ` Srivatsa S. Bhat
2013-09-06 12:31 ` Rafael J. Wysocki
2013-09-10 6:52 ` Viresh Kumar
2013-09-10 8:47 ` Srivatsa S. Bhat
2013-09-01 6:26 ` [PATCH 1/2] cpufreq: don't allow governor limits to be changed when it is disabled Viresh Kumar
2013-09-01 13:29 ` Rafael J. Wysocki
2013-09-01 13:26 ` Rafael J. Wysocki
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=5197493.kSPF7VUWqc@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=sboyd@codeaurora.org \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®