From: Xiaoguang Chen <chenxg@marvell.com>
To: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: viresh.kumar@linaro.org, rjw@sisk.pl, chenxg.marvell@gmail.com,
chenxg@marvell.com
Subject: [PATCH 1/2] cpufreq: Add governor operation ongoing flag
Date: Tue, 13 Aug 2013 15:09:25 +0800 [thread overview]
Message-ID: <1376377766-2594-1-git-send-email-chenxg@marvell.com> (raw)
__cpufreq_governor operation needs to be executed one by one.
If one operation is ongoing, the other operation can't be executed.
If the order is not guaranteed, there may be unexpected behavior.
For example, governor is in enable state, and one process
tries to stop the goveror, but it is scheduled out before policy->
governor->governor() is executed, but the governor enable flag is
set to false already. Then one other process tries to start governor,
It finds enable flag is false, and it can process down to do governor
start operation, So the governor is started twice.
Add the governor_ops_ongoing flag to check whether there is governor
operation ongoing, if so, return -EAGAIN.
Signed-off-by: Xiaoguang Chen <chenxg@marvell.com>
---
drivers/cpufreq/cpufreq.c | 9 +++++++++
include/linux/cpufreq.h | 1 +
2 files changed, 10 insertions(+)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index f0a5e2b..dfe0b86 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -1652,6 +1652,11 @@ static int __cpufreq_governor(struct cpufreq_policy *policy,
mutex_unlock(&cpufreq_governor_lock);
return -EBUSY;
}
+ if (policy->governor_ops_ongoing) {
+ mutex_unlock(&cpufreq_governor_lock);
+ return -EAGAIN;
+ }
+ policy->governor_ops_ongoing = true;
if (event == CPUFREQ_GOV_STOP)
policy->governor_enabled = false;
@@ -1684,6 +1689,10 @@ static int __cpufreq_governor(struct cpufreq_policy *policy,
if ((event == CPUFREQ_GOV_STOP) && !ret)
module_put(policy->governor->owner);
+ mutex_lock(&cpufreq_governor_lock);
+ policy->governor_ops_ongoing = false;
+ mutex_unlock(&cpufreq_governor_lock);
+
return ret;
}
diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
index 90d5a15..8d3eac2 100644
--- a/include/linux/cpufreq.h
+++ b/include/linux/cpufreq.h
@@ -111,6 +111,7 @@ struct cpufreq_policy {
struct cpufreq_governor *governor; /* see below */
void *governor_data;
bool governor_enabled; /* governor start/stop flag */
+ bool governor_ops_ongoing;
struct work_struct update; /* if update_policy() needs to be
* called, but you're in IRQ context */
--
1.8.0
next reply other threads:[~2013-08-13 7:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 7:09 Xiaoguang Chen [this message]
2013-08-13 7:09 ` [PATCH 2/2] cpufreq: Only do governor start after successful stop Xiaoguang Chen
2013-08-14 5:23 ` Viresh Kumar
2013-08-14 7:38 ` Xiaoguang Chen
2013-08-14 5:21 ` [PATCH 1/2] cpufreq: Add governor operation ongoing flag Viresh Kumar
2013-08-14 7:36 ` Xiaoguang Chen
2013-08-14 7:48 ` Viresh Kumar
2013-08-14 8:19 ` Xiaoguang Chen
2013-08-14 8:22 ` Viresh Kumar
2013-08-14 8:50 ` Xiaoguang Chen
2013-08-14 8:54 ` 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=1376377766-2594-1-git-send-email-chenxg@marvell.com \
--to=chenxg@marvell.com \
--cc=chenxg.marvell@gmail.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--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;
as well as URLs for NNTP newsgroup(s).